Re: Database Access
From: Kent Smith (ksmith_at_ipsoinc.com)
Date: Tue, 24 Feb 2004 13:28:58 GMT
On Tue, 24 Feb 2004 04:34:29 -0500, J.J. Holiday <email@example.com>
>On Tue, 24 Feb 2004 01:54:40 GMT, Kent Smith <firstname.lastname@example.org>
>>Then the best approach is to use ASP security. There are dozens of
>>good books out there that give cookbook approaches; this is a very
>>common thing to do. Make sure you know if you are using ASP or
>>ASP.NET (they are very different). ASP has pages with a .asp
>>extension, ASP.NET has pages with .aspx extensions.
>I'm using ASP (Not ASP.NET). There seems to be a myriad of books
>available. Can you recommend one or two that have information on how
>to do what I need done.
>BTW, thank you for your help.
When I did it for the first time, I used "ASP 3.0 A Beginner's Guide"
by Mercer. The basic thing to do is to create a session object to
hold the login state (true/false). Then have each page check the
session variable to see if it is allowed to display things that are
only visible to users who are logged in. If the session is not logged
in, then render a read-only page. If the session IS logged in, then
render an updatable page.
But like I said, this is a very common thing to do, any good ASP
development book should give you examples.
Kent Smith * IPSO Incorporated
Business * Technology * Solutions
Financial Services and Accounting Systems Consulting