Some restrictions may prevent you from saving your Access database as an MDE
file:
You must have password access to the Visual Basic code.
If your database is replicated, you must first remove replication
(replication: The process of copying a database so that two or more copies
can exchange updates of data or replicated objects. This exchange is called
synchronization.).
If your Access database references another Access database, or add-in
(add-in: A supplemental program that adds custom commands or custom features
to Microsoft Office.), you must save all Access databases or add-ins in the
chain of references as MDE files.
Additionally, 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.
To save an Access database that employs user-level security as an MDE file,
you must meet the following requirements before you can proceed:
You must join the workgroup (workgroup information file: A file that Access
reads at startup that contains information about the users in a workgroup.
This information includes users' account names, their passwords, and the
groups of which they are members.) 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 (owner: When security is
being used, the user account that has control over a database or database
object. By default, the user account that created a database or database
object is the owner.) of any tables in the database.
Your user account must have Read Design permissions for all objects in the
database.
