Custom log-in screen: remember me

[hbrems]

Dear all,

I'm creating a custom log-in screen (with user name & password). At this stage, when a user logs in with the correct details, I'm storing his name in a table, tblcurrentuser.

Later when I need the user's name I can just look into this table and add his name to an automatic generated e-mail, a report, etc.

However, having a table to store just 1 name, or just a few variables seems not the way to go.

On the other hand I would like to include a 'remember me' functionality, so the user doesn't need to type his log-ins each time he starts the application.

Can someone point me in the right direction?

Kind regards,
Hans B.

 

[KenHigg]

You can show them how to create a short cut with their login credentials (sp?) in the command line - ?

(See command line options)

 

[hbrems]

You can show them how to create a short cut with their login credentials (sp?) in the command line - ?

(See command line options)

Too complicated. I was maybe thinking global variables, but then the 'remember me' function would not work.

 

[KenHigg]

I would scrap the whole Access security thing anyway. Is that out of the question as well?

 

[hbrems]

I would scrap the whole Access security thing anyway. Is that out of the question as well?

Well, it's a multiuser application, with currently just 2 users, but with potential for more.

It would be nice to at some point have some control over who enters the application.

You know what, I will forget about the entire 'remember me' feature and use global variables instead. It saves me a headache...

Kind regards,
Hans B.

 

[KenHigg]

A home grown security schema isn't that hard to do and gives you complete control. I was thinking you could use a network id to figure out who the user is, etc

 

[missinglinq]

Besides which, providing "remember me" capability is fine for a web-site with nothing more critical than your list of favorite Cajun recipes or a forum on RPGs, but it's not very appropriate if you're worried about real security on a database!

Ken's advice on rolling your own security scheme is right on the money! Access' native security is such a mare's nest that Micro$oft finally dropped it altogether with Access 2007.