I have a database application for internal use at my company that often requires frequent updates. All users login via an .mde file which must be replaced after any updates.

Typically I have a setup program which the user reruns to update their code but what I'd like to do is run an automatic update that would copy over their local .mde file and then restart the application.

How can I tell Access to restart the current database? Or is there a better method? I figure there may be a .bat command or API call but don't know enough of either. Can anyone help?

I'm not sure what your asking, but here is some info about MDE files.

If your database contains Microsoft Visual Basic code, saving your Microsoft Access database as an MDE 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 Access database will be reduced due to the removal of the code. Additionally, memory usage is optimized, which will improve performance.

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 using the properties or methods of the Microsoft Access or VBA Object models — 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. Any tables, queries, data access pages, or macros in an MDE file can be imported into another Access database, but no forms, reports, or modules can be imported into another Access database.
Caution Be sure to save a copy of your original Access database. If you need to modify the design of forms, reports, or modules in an Access database saved as an MDE file, you must open the original Access database, modify it, and then save it as an MDE file again. Saving an Access database containing tables as an MDE file creates complications reconciling different versions of the data if you need to modify the design of the forms, reports, or modules later. For this reason, saving a Access database as an MDE file is most appropriate for the front-end database of a front-end/back-end application.

Caution You won't be able to open, convert, or run code in a Microsoft Access 2000 MDE file in future versions of Microsoft Access. The only way to convert a Microsoft Access 2000 MDE file to a future version will be to open the original Access database the MDE file was created from, convert it, and then save the converted Access database as an MDE file.

Important Some restrictions may prevent you from saving your Access database as an MDE file:

If your Access database is secured with user-level security, you must meet certain criteria. Learn about using other forms of security with an Access database that is saved as an MDE file.


You must have password access to the Visual Basic code. Learn about protecting Visual Basic code.


If your database is replicated, you must first remove replication system tables and properties.


If your Access database references another Access database, or add-in, you must save all Access databases or add-ins in the chain of references as MDE files.
From MS Access Help - Working With MDE Files