Microsoft Access contains a feature-full security system. Access permissions may be set either on individual database
users or on groups of users. These permissions extend to the tables, queries, forms, reports and macros.
Permissions
include read, insert, update and delete. There also special permissions which allow design changes and other database
administration functions.
We will be adding new examples to this section from time to time so check back periodically.
You can also protect
your visual basic code in several ways: Module passwords, Visual Basic password and creating an MDE file. The MDE file
method is the most secure way to protect you VBA code because the code is compiled. Compiling changes the code to what is
called Object code which can not be read my a human without tremendous difficulty. A side benefit of creating an MDE file is
that the database will be a little smaller and will be a little better optimized for memory usage.
When establishing
user and group permissions on a database the system will create what is called a Work Group Administration file (MDW). This
file contains all the user and group definitions for your computer system. All the object level permissions are stored in the
MDB or MDE file.
Aside: Note
that you can implement a robust security scheme by creating a custom interface - including opening forms and permissions assigned
programmatically in the form data interface. To see an example of such an interface see our
DB Security Method. A simple method to obtain low level
security is to hide objects, such as the database window, hide or remove toolbar menu options, hide or disable form menu choices and
tabbed form tabs.
Warning: We recommend that you do not use a Microsoft Access database for truly sensitive
data - such as medical records, employee records, voting systems, etc. Programs exist which can break most Microsoft software
security schemes.
Topics
Manually Setting Database Password
Programmatically
Setting Access Password
Using Grant and Revoke
