User Level Security

[Susanne]

It has been years since I've done extension programming and so all my books
are "old." I've also never used user-level security before so it is new. As
I'm reading over how to apply it and how it works, I noticed that it updates
the "wif" file on my computer. When the database is passed on, how do I
attach this information with it? Also, the customer will want to be able to
make their own additions/changes, is this possible too? Do I use the
user-level security or create my own log-in information?

Also, when breaking up the db into the back-end and front-end, how do I get
the db to automatically pt to the correct location of the tables? If I need
to update the forms or any part of the database, is there a way to update it
without losing the info in their tables?

Microsoft also used to have a developer's edition where you could package
your "software" so it would so an installation. Is that still used? What is
it now?

Oh, we are using Access 2003.

Thanks for any and all help!

 

[Arvin Meyer [MVP]]

Access 2003 is the last version to use User-Level Security. The newer format
in Access 2007 cannot, although the security developed in earlier versions
will be maintained as long as the file format is mdb.

Here is some of the best available information on User-Level Security:

Security FAQ
http://support.microsoft.com/download/support/mslfiles/SECFAQ.EXE

Lynn Trapp's summarization:
http://www.ltcomputerdesigns.com/The10Steps.htm

KB articles:
http://support.microsoft.com/default.aspx?scid=KB;en-us;q165009
http://download.microsoft.com/download/access97/faq1/1/win98/en-us/secfaq.exe
http://support.microsoft.com/default.aspx?kbid=325261

Joan Wild's articles:
http://www.jmwild.com/security02.htm
http://www.jmwild.com/security97.htm
http://www.jmwild.com/SecureNoLogin.htm
http://www.jmwild.com/Unsecure.htm