SteveCarey,
I'd appreciate the document on access security, always interested in picking up nuances when I can. Please send it to IntuitiveAccess@Yahoo.com
Thanks
New9,
I have used home-made security in the past when I am more concerned about identifying a user than actually securing a database. For instance, when the database is not critical and only used by a couple of users. The only advantage is that the administration can be built into the database and look more seamless. However, if you're interested in actually securing a database, anyone with minimal MS Access knowledge could hack your database in about 3 minutes if they can only type with one hand.
Here is how you do it:
1) Create a new database
2) Select "Get External Data" "Link Tables"
3) Select the file with your passwords table in it
4) Link the table
5) Open the table and get the admin ID and password
6) Log in to your database using the Admin ID and pw.
See the holes? A way that is slightly more secure (only slightly) is to use the Environ function to return the Win NT login as suggested by Pezamystik above. This way the usernames and passwords are not stored in the database at all. This means you can only access the database if you're signed in on that computer.
The downside is that if you walk away from your desktop, anyone can sit down at your computer and access the database as you. However, this same thing occurs with Access security if you leave the database open and walk away. There are ways to automatically detect and log out an idle user in Access which fixes this.
You need to determine how secure you want your database. If you just want to identify a user, just have them choose their name from a combo box and forget the pw altogether.
Jonathan
________________________________________
It is not fair to ask of others what you are unwilling to do yourself.
-Eleanor Roosevelt