How to Preserve Access Data When Creating an ACCDE File
Question details
The user wants to secure a Microsoft Access database by converting it to an ACCDE file, but needs to ensure that production data is not lost or overwritten during future application updates.

- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Deploying a secure Access application to users while maintaining editable and persistent production data.
- Observed behavior
- Converting an entire unsplit ACCDB database to ACCDE locks the design and code, but replacing that ACCDE file later will overwrite any new data entered by users. The application code needs to be separated from the stored data.
Create a full backup of your original ACCDB database file before attempting to split the database or publish it as an ACCDE file.
Split the Database into a Front End and Back End
Separating your database ensures that application objects (forms, reports, code) are independent of your production data (tables), allowing safe ACCDE deployment.
An ACCDE file restricts users from designing forms or reports and hides VBA code. However, if tables are kept inside the ACCDE, replacing the file during a software update will erase all the data users have entered. Splitting the database solves this by isolating tables into a separate file.
Launch Microsoft Access and open the ACCDB file that currently contains both your tables and application objects.
Navigate to the 'Database Tools' tab on the ribbon and click on 'Access Database' in the Move Data group to launch the Database Splitter wizard.
Follow the wizard prompts to split the database. This creates a new 'back-end' file containing only your tables, while your current file becomes the 'front end' with linked tables.
With the front-end database open, go to 'File' > 'Save As', select 'Make ACCDE' under Save Database As, and click 'Save As' to generate the locked executable file.
Store the back-end database on a shared network location. Distribute a separate copy of the front-end ACCDE file to each user's local computer.

Need a lightweight and fully compatible Office suite? Try WPS Office
While Microsoft Access handles complex relational databases, your daily workflow involving text documents, spreadsheets, and presentations requires a versatile, fast, and cost-effective solution. WPS Office is a highly compatible, lightweight, and free alternative to Microsoft Office. It features a familiar tabbed user interface for a seamless migration, allowing you to handle regular office tasks effortlessly without expensive subscriptions.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install the Software: Run the lightweight installation file and follow the simple on-screen instructions to complete the setup.
- 3. Open Your Files: Launch WPS Office to instantly open, edit, and save your existing Office documents seamlessly.

Frequently Asked Questions
What exactly does an ACCDE file do in Microsoft Access?
An ACCDE file is a compiled, locked-down version of an Access database. It allows users to edit data, run queries, and execute macros, but it strictly prevents them from modifying form or report designs and blocks viewing or editing of VBA code.
What happens if I don't split my database before creating an ACCDE?
If you deploy a single, unsplit ACCDE file, any new data entered by your users is saved directly inside that file. If you ever need to release an updated version of your application, replacing the old ACCDE file will overwrite and permanently delete all the production data users have entered.
Can multiple users share the same ACCDE front-end file on a network?
It is highly recommended against having multiple users open a single shared front-end file over a network. Instead, you should provide each user with their own individual copy of the ACCDE front-end file stored on their local computer to prevent database corruption and improve overall application performance.




