← Insights

Access database stopped working after an Office update: what to check

An Access application that ran for years can fail the morning after an Office update. These are the usual causes, in the order worth checking them.

An Access application that has run without trouble for years can fail the morning after Office updates itself. Nothing in the database has changed, which makes the fault confusing, but the causes fall into a small number of groups. Before trying anything, take a copy of the database files and note the exact wording and number of the error message.

1. A missing or broken reference

This is the most common cause, and the most misleading. Access applications rely on code libraries listed under Tools > References in the VBA editor. If an update removes or replaces one of them, the list shows it as MISSING.

The confusing part is the symptom. A missing reference rarely produces an error that names the library. Instead, ordinary built-in functions such as Left, Date or Format start failing, often with “Compile error: Can’t find project or library”, in code that has nothing to do with the missing item.

What to check:

  • Open the VBA editor and look at Tools > References for any entry marked MISSING.
  • Run Debug > Compile. The first line it stops on usually points to the problem.

The fix is to repair the reference or, better, to remove the dependency on a version-specific library altogether.

2. Office changed from 32-bit to 64-bit

Office is now installed as 64-bit by default. If a PC was rebuilt or Office was reinstalled, an application written for 32-bit Access may suddenly be running in 64-bit Access.

The usual message is that the code “must be updated for use on 64-bit systems”. Windows API declarations in the VBA need to be revised, and some older 32-bit ActiveX controls have no 64-bit equivalent. This needs a developer, and it is covered in more detail in the article on 32-bit to 64-bit VBA.

3. The file is no longer trusted

If the application opens but buttons do nothing and no code runs, Access may have disabled the VBA. An update, a new PC or a move to a different folder can mean the database is no longer in a Trusted Location, and files that arrived by email or download can be blocked outright.

Check File > Options > Trust Center > Trust Center Settings > Trusted Locations. In a managed environment these settings are often controlled by IT policy, so the change may have to be made there.

4. A compiled file that no longer matches

Many applications are distributed as a compiled ACCDE (or older MDE) file. A compiled file only runs in the kind of Access it was built for. If Office moves from 32-bit to 64-bit, or to a significantly different version, the compiled file will refuse to open.

The fix is to rebuild the compiled file from the original ACCDB source in the new version. This is why it matters to know where the source file is. If only the compiled file survives, the code cannot be edited, and recovery becomes a much larger job.

5. Stale compiled code inside the database

Access stores a compiled copy of the VBA alongside the source. Occasionally an update leaves that compiled copy out of step, producing crashes or odd errors as soon as code runs. A developer can clear and rebuild it, or import every object into a fresh, empty database, which often cures unexplained instability.

6. A fault in the update itself

Occasionally the update is the problem. Microsoft has, from time to time, released Office builds that broke something in Access, and has then issued a fix within days. If several unrelated databases fail in the same way on the same morning, this is the likely cause. Rolling Office back to the previous build is a legitimate short-term answer while a fix is released.

What not to do

  • Do not let several people keep trying to open a file that is reporting errors.
  • Do not run Compact and Repair on your only copy.
  • Do not keep editing the live file to “see if this helps”. Work on a copy.

When to get help

If the reference list and the trusted location are both in order and the application still fails, the cause is in the code or the file itself, and guesswork tends to make it worse. With the exact error text and a copy of the files, a specialist can usually find the cause quickly.

Need help with this on your own system?

Talyon repairs, supports and modernises business-critical Microsoft Access applications. Describe what is happening and what the system does, and start with a conversation.