Types of permissions (MDB)
Note The information in this topic applies only to a Microsoft Access database (.mdb).
The following table summarizes the permissions that you can assign.
| Permission | Permits a user to |
|---|---|
| Open/Run | Open a database, form, or report, or run a macro in a database. |
| Open Exclusive | Open a database with exclusive access. |
| Read Design | View tables, queries, forms, reports, or macros in Design view. |
| Modify Design | View and change the design of tables, queries, forms, reports, or macros; or delete them. |
| Administer | For databases, set a database password, replicate a database, and change startup properties.
For tables, queries, forms, reports, and macros, have full access to these objects and data, including ability to assign permissions. |
| Read Data | View data in tables and queries. |
| Update Data | View and modify, but not insert or delete, data in tables and queries. |
| Insert Data | View and insert, but not modify or delete, data in tables and queries. |
| Delete Data | View and delete, but not modify or insert, data in tables and queries. |
Notes
- Some permissions automatically imply the selection of others. For example, the Update Data permission for a table automatically implies the Read Data and Read Design permissions because you need these to modify the data in a table. Modify Design and Read Data imply Read Design. For macros, Read Design implies Open/Run.
- To design forms, reports, macros, and modules in a multiuser environment, you must open a Microsoft Access database exclusively, which means you must have Open Exclusive permission on the Access database.
- In general, if you want users to be able to access a linked table, grant them Read Data and Read Design permissions on the table in the back-end database, and Modify Design permission on the table link defined in the front-end database so that they can conveniently re-link the table. If you want to restrict all access to the back-end table but still allow users to view the data and re-link the tables, remove all permissions on the back-end table and use queries in the front-end database with their RunPermissions property set to Owner's.