Database ASP.NET form approval process

Hi there,

I have a question I am not sure what category it belongs since it touches ASP.NET, SQL2000 and document routing concepts.
I have an ASP.NET application that has a SQL2000 database as a back end.
This ASP.NET application has several forms that need to be filled in (each form is based on a table in the database) and then they need to be approved by 3 gatekeepers (3 different employees of our organization).
I am not sure what is the correct way to implement the approval process.
(One idea I have is to have a table for each form with the log in ID of the people that need to approve it and then based on the users log in ID to allow only to the above users to click on a button.... but this idea seems to "small approach" based on the fact that in the near future we are going to have dozens of forms that will need to be approved).
Any ideas of what is the proper approach of database generated documents approval process would be very much appreciated.

Thank you,

Liliana
liliana@cakerie.com
ronchonchonAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ralf KlattEmployee in Civil ServiceCommented:
Hi,

It's never easy to imagine what else could be necessary for an approval process in a company you do not really know about ... an "interesting" article (at least!) can be found at:

http://www.informit.com/articles/article.asp?p=171030&seqNum=8&rl=1


Best regards,
Raisor
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
margantCommented:
Well how about grouping users into an approval group, so for example one database design could be:

ApprovalGroup
AGID PageID ApprovedOrNot

ApprovalGroupMembersAndState (linking table)
AGID UserID ApprovedOrNot

To use these tables you will have all required people approving which will add ApprovedOrNot into ApprovalGroupMembersAndState and once all of them approved you will change ApprovedOrNot in the ApprovalGroup table to true.

You may also choose to add a role-based authentication based on this approval group scenario or something of this sort. For more info on that please check out
http://www.codeproject.com/aspnet/formsroleauth.asp

Hope that helps,
A.M.
0
Ralf KlattEmployee in Civil ServiceCommented:
Hi,

I think that http://www.informit.com/articles/article.asp?p=171030&seqNum=8&rl=1 gave at least the same good overview to this question as http://www.codeproject.com/aspnet/formsroleauth.asp did ... if the provided answers are not to be deleted, they should at least be split!


Best regards,
Raisor
0
margantCommented:
pinalDave, Raisor
I completely agree about a split, i think Raisor's link very informative, i learned quite a bit from it myself :)
-A.M.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Development

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.