Convert ACCDE to MDB

A legacy program may require an .mdb database when the available Access application is an .accde file. The practical solution is to create a new MDB and transfer the data and any objects that Access can expose; an ACCDE cannot be restored to its editable source format.

What the ACCDE format is

ACCDE is Microsoft Access's compiled deployment format, created from an .accdb database. It retains tables and compiled application objects, but removes editable VBA source code and prevents design changes to forms, reports, and modules. It is commonly distributed as the front end of an Access application while the developer keeps the original ACCDB.

Full desktop editions of Access 2007 and later can create and open ACCDE files. Access Runtime can run an ACCDE application, but it does not provide the database-design and import tools required for migration.

What the MDB format is

MDB is the Access 2000–2003 database format, based on the Jet/ACE database engine. It can contain tables, queries, forms, reports, macros, and modules, and remains necessary for some legacy Access applications, integrations, and software that cannot open ACCDB files.

MDB has a maximum database size of approximately 2 GB and cannot represent features introduced after the Access 2000–2003 format, including some newer data types and application features. A modern MDB may still require Microsoft Access or the Microsoft Access Database Engine to open.

How to create an MDB from an ACCDE

Access has no supported Save As command that converts an ACCDE back to ACCDB or MDB. Use the full desktop edition of Microsoft Access to create an MDB and import the recoverable content.

1. Make a working copy of the ACCDE and confirm that you have permission to extract its data and objects.
2. Open Microsoft Access and create a blank database. Choose File → Save As → Access 2002–2003 Database (*.mdb). If that option is unavailable during creation, save the blank database as an MDB using the format-selection prompt.
3. In the new MDB, choose External Data → New Data Source → From Database → Access, select the ACCDE, and choose the import option.
4. Import the tables and queries that Access exposes. Import only objects that the source permits; an ACCDE does not provide the original editable form, report, module, or VBA source.
5. If the ACCDE uses linked tables, determine whether the MDB should contain copied data or links to the existing back-end database. Use External Data → Linked Table Manager to update link paths when necessary.
6. Open the MDB and test relationships, queries, data types, indexes, and application behavior. Recreate forms, reports, macros, or modules manually when they cannot be imported, then test the result with the exact Access version and legacy program that will use it.

For a data-only migration, importing or exporting the tables is usually sufficient. If the ACCDE is only a front end, its tables may be linked to a separate MDB, ACCDB, SQL Server, or other back end; importing the front end will not automatically copy that external data.

Tools and online conversion limits

Microsoft Access is the appropriate desktop tool because it understands Jet/ACE tables, relationships, queries, and Access object definitions. Access Runtime cannot perform this migration. General file converters cannot reliably preserve an Access application's dependencies or compiled behavior.

No reputable online converter can turn an ACCDE into a fully editable MDB while restoring removed VBA source and locked design objects. Web services may handle isolated table-data exports, but uploading an Access database can disclose sensitive data and will not preserve the application. Use an online service only for non-confidential, data-only conversion after verifying its supported Access versions and output schema.

Compatibility and quality caveats

The original ACCDB is required for VBA editing. ACCDE compilation removes the VBA source; importing or copying a module cannot reconstruct it. Missing references, external libraries, linked files, and database connections can also cause errors in any surviving compiled behavior.

ACCDB-only features may be lost or require redesign in MDB, including attachments, multivalued fields, calculated fields, newer encryption options, and data types or expressions unsupported by the Access 2000–2003 format. Queries, relationships, field properties, and user-interface behavior may need manual correction after import.

If the required result is a complete editable Access application rather than a data container, obtain the original ACCDB or its source project from the developer. An ACCDE-to-MDB procedure can recover compatible data and selected objects, but it cannot reverse the protections built into the deployment file.