"Rick Brandt" <ri*********@hotmail.com> wrote
What do you have, some sort of home-grown
login system?
I feel compelled to mention that, if Rick is correct about this, homegrown
login systems are easy for an experienced user to crack, so you shouldn't
count on them to protect much of anything.
Don't count on even Access' "labrynthine*" security to protect anything that
is worth US$150 to someone who wants it -- that's what very capable cracker
software, oops, I mean "password recovery software" sells for over the
Internet. I haven't tried any lately, but a few years back, I tried the
"free trial" version that was limited to 3-character passwords and it worked
just-fine-thankee.
* as characterized by Roger Jennings in his
"Access 2 Developer's Guide" and it hasn't
gotten any less "twisty" since
That said, if all you are trying to do is to keep users from stumbling over
their own fingers, it may be all you need. If that is the case, you might
want to look at
http://www.mvps.org/access/api/api0008.htm for code to use
the Windows API to get the user's network login name, so the user does not
have to enter anything... just open the database application and start work.
For "persisting" (it always grates on me to see "persist" used as a verb)
user or system information over a longer period and across logouts and
relogins, I use a combination of tables in the shared tables database and in
the front end databases on each user's machine. Seems to me I put an article
on that subject up on
http://accdevel.tripod.com.
Larry Linson
Microsoft Access MVP
