Access Evolved
FAQ · Project planning, cost, and security

What should we back up before changing an Access database?

Before any repair, upgrade, or migration, preserve the complete application, data, related files, connection information, and a record of the environment needed to run it.

Short answer

Before any repair, upgrade, or migration, preserve the complete application, data, related files, connection information, and a record of the environment needed to run it.

What this means in practice

Backups should be copied to a separate protected location and tested. A backup that has never been restored is only an assumption.

✓Front-end and back-end Access files.
✓Workgroup, configuration, template, import, export, and attachment files.
✓External SQL databases and linked data sources.
✓VBA source exports, references, connection settings, and scheduled tasks.
✓Reports or control totals used to validate recovery.
✓A list of Office version, bitness, trusted locations, drivers, and dependencies.

The practical next step

Create a time-stamped baseline before changes and keep multiple recovery points during the project. Never perform experimental repair work on the only available copy.

Related guidance

Explore the relevant service →Read related guidance →Discuss your system →

This answer provides general guidance. The right recommendation depends on your application, data, users, licensing, and business requirements.