This behavior does not occur with MDB files and can be avoided by renaming MDE files so that they have the .mdb file name extension.
NOTE: You can modify the design of forms, reports, or modules only by modifying a form, report, or module in the original database and saving it as an MDE file again; therefore, it is important to keep a copy of the original database.
If the MDE file is located in the same folder as the MDB file, you must rename the MDE file so that its name is different from that of the original MDB file. For example, if your file is named Mergedata.mde, you may want to rename it Mergedata2.mdb. By giving the new file a different name from that of the original file, you also reduce the possibility of accidentally overwriting the original MDB file with the new MDB file.
By changing the file name extension of a database from MDE to MDB, you do not affect the special characteristics of an MDE file. Users of the database are still prevented from doing the following:
- Creating, viewing, or modifying 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 Visual Basic for Applications Object models; an MDE file contains no
source code.
- Changing the Visual Basic for Applications project name in your database by using the Options dialog box.
- Importing or exporting forms, reports, or modules.