Share via

About using a database password and user-level security with a Microsoft Access database that is saved as an MDE file

  • Article

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Creating an MDE file secures the forms, reports, and Microsoft Visual Basic code in your Microsoft Access database, without requiring users to log on or requiring you to create and manage the user accounts and permissions that are needed for user-level security. However, if you define a database password or user-level security before saving an Access database as an MDE file, those features will still apply to an MDE file created from that database. If your Access database has a database password or user-level security defined and you want to remove these features, you must do so before saving it as an MDE file. For information on removing a database password, click aa831142(v=office.10).md. For information on removing user-level security, click aa831379(v=office.10).md.

To save an Access database that was secured with user-level security as an MDE file, you must meet the following requirements before you can proceed:

  • You must join the workgroup information file that defines the user accounts used to access the database, or that were in use when the database was created.

  • Your user account must have Open/Run and Open Exclusive permissions for the database.

  • Your user account must have Modify Design or Administer permissions for any tables in the database, or you must be the owner of any tables in the database.

  • Your user account must have Read Design permissions for all objects in the database.