Shared-level security involves setting a password on a database. Setting a database password is a simple solution to protect a database for a small group of people. This can be effective in situations where anyone who can access the database is permitted to insert, delete, or update the data and update any of the objects ( for example, forms, reports, and so on) in the database.
When shared-level security is applied to a database, the user is prompted for a password each time that database is opened. Shared-level security only protects the MDB file on which the password is set. When the correct password is entered, the user gains full access to that database including all data and all objects contained in that database.
Be aware that setting a database password only affects attempts to access the database using the Microsoft Jet Engine. See Encoding a Database for more discussion.
User-level security (discussed later) does not override the database password. User-level security will require the user to log on to use a database in Access. However, if the database the user opens is also password protected, the user will have to enter the shared-level password after entering their own username and password.
16.2.1. Shared-Level Secured Back-End Databases
Be careful while linking to tables in a shared-level protected database. When your front end links to tables in the protected back-end database, you will be required to specify its password. After ...
With Safari, you learn the way you learn best. Get unlimited access to videos, live online training,
learning paths, books, interactive tutorials, and more.