Table security

[funger]

I have a database that consists of a frontend and a backend. I need to be able to secure the tables in the backend so that I can access them through code, and the interface, but so that the user can not access the tables directly, nor can they import the table objects into a new database.

How would I go about doing this?

Thanks!
Jim

 

[RickSpr]

You must use Access user-level security, and the best way to apply it is to use the User-Level Security Wizard.

First download the Microsoft Security FAQ at

http://www.abcdataworks.com/Developers/SECFAQ.doc

(courtesy of member JeremyNYC). It's an in-depth document that answers a great many questions about how to secure Access databases from versions 2 to 2000.

Then prepare yourself by reading the Help file topics on security. The Access user-level security system is complex, but if you take the time to understand the principles of it, it may save you from having to start over from scratch.

Next, look at the Help file topic on running the User-Level Security Wizard. Follow the steps carefully. If you're not certain you understand what it's telling you to do, and why it needs to be done, consult the SECFAQ or the other help topics again, or come back here for an explanation.

If you follow the instructions carefully, you'll find that setting up your security is somewhat tedious, but not difficult, and that your users can't get to your tables by any means (unless they work for the NSA or CIA!).

If you run aground, do a search for other threads on security, and/or search for FAQs in the Tek-Tips forums. It's likely somebody else has had the problem before. If you still can't find help, come back and post. We'll be here to help.

BTW, if anybody tries to tell you that your database can be secured by simpler means, don't believe them. You specifically said you want to be sure the users can't import your tables into another database. The only other way to do that is with a database password, and there are two problems with that: (1) There are utilities available elsewhere on the Internet for cracking database passwords, and (2) Your users will have to have access to the password in order to use the database. Even if it's "hidden" in a batch file or shortcut, it would be easy for them to discover it if they have a little knowledge of how Windows works.

Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein