Convert Access MDB and MDE Databases to ACCDB and ACCDE Safely
Question details
Convert a split Access application to ACCDB and ACCDE while maintaining compatibility and reliable deployment.

- Product
- Microsoft Access 2013
- Device & OS
- not provided
- Scenario
- The application has an MDE front end and an MDB back end, and the user wants to evaluate and test conversion to newer Access formats.
- Observed behavior
- The desired result is a tested ACCDE front end linked to an ACCDB back end, with working application features and deployment procedures.
Locate the original editable MDB front-end source; an MDE alone cannot be converted into an editable ACCDB or rebuilt as an ACCDE. Check whether the application relies on MDB features such as user-level security or replication, which ACCDB does not support.
Convert and test the split Access application
Use this approach when the original front-end source is available and the application is suitable for ACCDB.
Work on copies in a test environment before changing the deployed application. Confirm that users have compatible Access or Access Runtime versions and that the ACCDE architecture matches their 32-bit or 64-bit installation.
Make copies of the editable MDB front end and the MDB back end. Close users' connections to the back end before converting its test copy.
Open the back-end MDB copy in Access 2013, then choose File > Save As > Save Database As > Access Database (*.accdb). Save it to a test location.
Open the editable front-end MDB copy and use File > Save As > Save Database As > Access Database (*.accdb) to create an ACCDB front end.
In the ACCDB front end, use External Data > Linked Table Manager to update the links to the test ACCDB back end. Test forms, reports, queries, and VBA; in the VBA editor, check Tools > References and use Debug > Compile to identify errors.
In Access 2013, open the tested ACCDB front end and choose File > Save As > Save Database As > Make ACCDE. Test the resulting file with the intended Access or Access Runtime installation, linked back end, and deployment procedure before rollout.

Keep the MDB and MDE formats when conversion is unnecessary
Consider retaining the existing formats when they meet business requirements or the application depends on features unavailable in ACCDB.
Use WPS Office alongside your Access database
WPS Office is a free, lightweight alternative for everyday documents, spreadsheets, and presentations, with a familiar interface that makes migration easier. It does not convert MDB or MDE databases or replace Microsoft Access for this task.

Frequently Asked Questions
Can I convert an MDE directly to an ACCDE?
No. An MDE does not contain the editable source needed to rebuild the application. Locate the original MDB front-end source, convert it to ACCDB, and then use File > Save As > Save Database As > Make ACCDE.
How do I reconnect the front end to the converted back end?
Open the ACCDB front end and use External Data > Linked Table Manager to update its links to the ACCDB back end. Test the links from the location and user environment intended for deployment.
Will ACCDB preserve MDB user-level security and replication?
No. ACCDB does not support those MDB features. Review how the application uses them before conversion and plan an alternative if they are required.
Do I have to convert an Access 2002–2003 MDB?
Not necessarily. Access 2013 can work with that MDB format. Test the existing application and base the decision on compatibility, supported features, and business requirements.
Can users open the ACCDE with a different Access bitness?
An ACCDE created in 32-bit Access cannot run in 64-bit Access, and vice versa. Create and test the ACCDE using the architecture required by the target installations.




