From the Help file:
f your database contains Visual Basic code, saving your database as an MDE
file compiles all modules, removes all editable source code, and compacts
the destination database. Your Visual Basic code will continue to run, but
it cannot be viewed or edited, and the size of your database will be reduced
due to the removal of the code. Additionally, memory usage is optimized,
which will improve performance.
Saving your database as an MDE file prevents the following actions:
· Viewing, modifying, or creating forms, reports, or modules in Design view.
· Adding, deleting, or changing references to object libraries or databases.
· Changing code using the properties or methods of the Microsoft Access or
VBA Object models ¾ an MDE file contains no source code.
· Changing your database's VBA project name using the Options dialog box.
· Importing or exporting forms, reports, or modules. However, tables,
queries, and macros can be imported from or exported to non-MDE databases.
Any tables, queries, or macros in an MDE database can be imported into
another database, but no forms, reports, or modules can be imported into
another database.
Since it only affects VBA code, there's never any point making your back-end
database (the tables) an MDE. If you want to prevent your users from
changing the code (and gain a very slight performance edge), it probably
makes sense to conver the front-end database to an MDE.
--
Doug Steele, Microsoft Access MVP
<a rel="nofollow" style='text-decoration: none;' href="http://I.Am/DougSteele" target="_blank">http://I.Am/DougSteele</a>
"Anthony Webb" wrote in message
> Can anyone tell me the difference between an MDB and an
> MDE file and what they are used for.
>
> TIA
>
> Anthony
Office (other)