Is there an existing module for a user logon sequence in Access 2.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Rather than re-invent the wheel, I was wondering if there was an existing
user-level logon module that I could copy and modify. I.e.:

Login(ValidUserGUID)
+ collect username
+ collect password ('*' displayed)
+ Lookup username
+ encrypt user entered password
+ compare encrypted passwords (entered and stored)
+ return 0 if okay (fill in ValidUserGUID), 1 if unknown user, 2 if invalid
password

Or something similar.

thanks,
tony
 
Looks like that would work great if I wanted to use NT authentication. This
is for the back-end of a web site and I didn't want to use Windows
authentication. I was hoping for something simpler that I could do soley
within Access.

Any other thoughts?

thanks,
tony
 
Are you talking about doing this as a web interface? I don't believe there's
any way to do that using Access: you have to have forms on the web (ASP,
ASP.Net, or whatever), and interact with the Access database using whatever
data communication interface you're using (probably ADO)
 
I'm prototyping the workflow in Access. I will probably stay with Access,
but collect the data in a VB routine or Access Macro. When it moves to a web
page for the UI, then I will probably have to solve the problem again using
ADO or SQL if I end up going to SQL Server.

But I'd like to have a functioning Access app before I turn it over to the
web guy to put a UI on it that is consistent with the web site.

I guess the routine I'm missing is:
encryptString(seed, string)
With that, I can capture the password when originally entered and save it in
the DB. Subsequent authentication would be to encrypt the password (with the
same seed) that is entered when the user logs on to the application and then
compare the entered and stored strings. I don't see where Access has any
builtin encryption routine. If there is one, I'd take a pointer to it. If
not, are you aware of anyone who's built this simplistic authentication
mechanism. I don't want to create users in AD each time a new client creates
an account to get to informaiton.

Does this make sense?

thanks,
tony
 
Back
Top