It depends on what you mean and what your circumstances are. Access is not
very secure, so there is no fool-proof way to do this (depending on the
sophistication of your users, that is).
The first level, is to split your application into a Front-End (FE) and
Back-End (BE) where the BE has only the tables and the FE has everything
else, with the tables linked in. This will prevent your users from
modifying the table structure of the linked tables (in the FE), but if they
know enough to open the BE, you are still open to modifications.
To prevent this, you COULD create a Database Password for the BE that will
prevent them from opening it. This creates some complications for linking
the tables (you have to give the password when you do it). Another problem
with this is there are dozens of password cracking programs available that
will give you the Database Password.
The next level is to go to full-fledged Access Security. This is a big,
messy step, so you need to do some research and practice on a test database
first. The usual reference is the "Microsoft Access Security FAQ" that
Microsoft wrote many years ago. (Find it here:
http://www.rogersaccesslibrary.com/knowledge.html) It will answer most of
your questions, but some trade press books (Alison Balter's books come to
mind) also explain about setting up security. It is not for the faint of
heart, but once in place, it is much tougher to crack than the Database
Password (but still not impossible).
--
--Roger Carlson
Access Database Samples:
www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L