If making an mde file from an mdb file guaranteed a corruptionless environment, everyone would be using mde’s.
You can cause instant almost irreparable corruption to an mde or mdb file by attempting to open it with Word.
Any mdb or mde working on a networked configuration will almost always corrupt when there is a NIC failure.
Quoting from MS:
Saving your Access 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 — an MDE file contains no source code.
• Importing or exporting forms, reports, or modules. However, tables, queries, data access pages, and macros can be imported from or exported to non-MDE databases.
Notice there is nothing said about corruption.
The ways to minimize the probability of corruption are:
Always split your database into front end back end.
Make sure your code is optimized to the best of your knowledge.
Use Access security to insure that users can do absolutely nothing to your tables other than read them via forms and queries. Give design permission on anything to no one but yourself.
Additionally, if you are setting up for a network:
Be sure all NIC’S on user PC’s are fully operational and a good quality brand, i.e. 3Com.
Make sure all queries request and act on the smallest recordset possible.
Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@yahoo.com
