It is obvious that if you want to authenticate the user against a user
log-in record in a table, you have to create table in the said database and
provide a way for user/administrator to create user log-in information
before you can use it for logging in authentication.
You did not describe your situation in detail as to how your application
works and in what kind of environment. However, since you say "using
Access2003 and can get user's network login, I assume it is a LAN
environment. Now the question is why you want to re-invent the wheel when
you can easily control user's access to the SQL Server/database by using SQL
Server's built-in security features? Since your user uses a desktop app (MS
Access2003) he/she must log into the LAN/computer, you can use SQL Server's
Windows integrated security mode to control access to SQL Server/Database,
there is not need to ask user to log in again as long as the user logs into
the LAN computer.
"E. Kwong" <ekwong999AThotmail.com> wrote in message
news:(E-Mail Removed)...
> Using the script at
> http://www.mvps.org/access/api/api0008.htm
>
> , I'm able to get the user network login.. Now I would like to check this
> network login against a sql table. If there's a match, the user is
> allowed in, if not a popup mesage box would inform the user to contact me.
>
> I would like to do all these "behind the scene" without asking the network
> user to login again (i.e. programming a startup login form). What's the
> best way to go about this? Any pointer appreciated. Am using Access
> 2003 / Sql Server 2000
>
Similar Threads
