How to Fix Access 2016 Form Macros Not Running After Database Conversion
Question details
Users need to resolve an issue where form macros or VBA code fail to execute after a database is opened or converted in Microsoft Access 2016.

- Product
- Microsoft Access 2016
- Device & OS
- not provided
- Scenario
- Opening, upgrading, or converting an older Access database (.accdb or .mdb) in Microsoft Access 2016.
- Observed behavior
- Form macros and VBA code stop working or throw errors, often caused by a mismatch in Office bitness (32-bit vs. 64-bit) or broken VBA references.
Ensure your Access Trust Center settings are configured to allow macros to run, and create a backup copy of your database file before making any changes to VBA code or references.
Resolve VBA Reference Errors and Recompile the Database
Use this solution to identify broken library references and recompile your VBA project, which is the most common fix for macro failures after an Office upgrade.
When moving an older database to Access 2016, the system architecture might change (e.g., from 32-bit to 64-bit). This causes the database to lose track of essential library references required to run macros and VBA code.
Fixing broken references and compiling the code forces Access to re-evaluate all macros and ensure compatibility with the current installation.
Open your database in Access 2016. Press ALT + F11 on your keyboard to launch the Visual Basic Editor (VBE).
In the VBE, click on 'Tools' in the top menu bar, then select 'References'. Look through the checked items in the list for any entry that starts with the word 'MISSING:'.
Uncheck the box next to any 'MISSING:' reference. Scroll down to find the Access 2016 equivalent of that library (usually with a higher version number) and check it, then click 'OK'.
Click 'Debug' in the top menu and select 'Compile [Your Database Name]'. If there are syntax or bitness errors (like missing PtrSafe attributes in 64-bit), the compiler will highlight them for you to fix.
Compact and Repair the Database
Use this built-in Access tool to fix underlying structural corruption that might prevent form macros from executing correctly.
A Free and Lightweight Alternative for Your Daily Office Tasks
While WPS Office does not feature a database application like Microsoft Access, it is an exceptional, free alternative for your word processing, spreadsheet, and presentation needs. If you are dealing with complex Microsoft Office licensing or heavy resource usage, switch to WPS Office for a fast, user-friendly experience.
- 1. Download the Installer: Visit the official WPS Office website and click the download button for your operating system.
- 2. Install WPS Office: Run the setup file and follow the on-screen prompts to complete the lightweight installation.
- 3. Open Your Documents: Instantly open and edit your existing Microsoft Office files without losing any formatting.

Frequently Asked Questions
Why do my Access macros say 'Action Failed' after upgrading to Access 2016?
This usually happens due to deprecated macro actions, Trust Center security blocking the macros, or changes in the Office installation bitness (switching from 32-bit to 64-bit) which breaks the underlying VBA references.
How do I check if my Access 2016 is 32-bit or 64-bit?
Open Microsoft Access and click on 'File', then select 'Account'. Click the 'About Access' button. A new window will appear showing the full version number followed by either '32-bit' or '64-bit'.
How do I enable macros in Access 2016 Trust Center?
Go to File > Options > Trust Center. Click 'Trust Center Settings', then navigate to 'Macro Settings'. Select 'Enable all macros' (not recommended for unsafe files) or ensure your database is located in a 'Trusted Location' to allow macros to run safely.
Does recreating the AutoExec macro fix conversion issues?
Sometimes. Deleting and recreating the AutoExec macro can resolve initialization glitches during conversion, but if the issue lies in broken VBA library references or 64-bit incompatibility, you must resolve those in the Visual Basic Editor first.




