IN THIS CHAPTER
Understanding Jet security
Deciding on a security level to implement
Creating a database password
Using the /runtime option
Using the Current Database options
Manipulating users and groups
Securing objects by using permissions
Using the Access Security Wizard
Protecting Visual Basic code
Encrypting or encoding a database
Using the Trust Center
Although Access provides the interface to maintain security options, it is Jet that actually performs security functions. The Jet security model has changed little from Access 95 to Access 2003. Jet's security in those versions is a workgroup-based security model; all users in a workgroup are bound to the same security rules. The rules enforced for individual users may vary from user to user based on the permissions assigned to each user.
Microsoft removed the user-level security features from the new Access 2007 (
.accdb) format but retained the functionality to manage user-level security for previous versions of Access databases (
.mdb files). Microsoft retained the functionality in Access 2007 to manage user-level security for the older file formats; however, you can't set user-level security for an Access 2007 database. Other options, such as setting a database password, are available for all database versions.
In this chapter, you will use the database file
Chapter29.mdb. This is in an Access 2000 format database file that demonstrates all the functionality, including user-level security, not ...