Make an Access ACCDE Database Compatible with 32-Bit and 64-Bit Office
Question details
Make an Access ACCDE database available to users running both 32-bit and 64-bit Office.
- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- An ACCDE created with 32-bit Office needs to run in environments with different Office bitness.
- Observed behavior
- The existing ACCDE may produce a compatibility error in 64-bit Office.
In Access, select File > Account > About Access to check the Office bitness on each target system. Locate the editable source ACCDB and make sure you have access to full Access installations for compiling the required versions.
Update the VBA code and create separate ACCDE versions
Use the source ACCDB to prepare code for both Office bitnesses, then compile an ACCDE in each target environment.
An ACCDE compiled in 32-bit Access cannot be used as a universal 32-bit and 64-bit compiled file. Create a separate ACCDE using Access of the bitness where each version will run.
PtrSafe marks a Windows API declaration as compatible with 64-bit VBA, but it does not automatically correct parameter or return types. Use LongPtr for pointers and handles where appropriate; do not replace every Long with LongPtr. Conditional compilation is needed when declarations or code must differ between environments, such as older VBA versions.
Open the editable ACCDB in Microsoft Access. If you only have the ACCDE, obtain the source ACCDB from its developer before changing or recompiling VBA code.
Press Alt+F11 to open the VBA editor and review Declare statements in the modules. Add PtrSafe where required and check pointer and handle types against the relevant Windows API definitions.
In the VBA editor, use #If VBA7 Then or #If Win64 Then blocks when a declaration or code path must differ by VBA version or bitness. A correctly written PtrSafe declaration can support both 32-bit and 64-bit VBA, so separate declarations are not always necessary.
In the VBA editor, select Debug > Compile and fix any reported code or reference errors. Check Tools > References for libraries that are unavailable in the target environment.
In 32-bit Access, open the updated ACCDB and select Database Tools > Make ACCDE. Repeat the compile and Make ACCDE process in 64-bit Access, saving the output under a distinct name.
Open the 32-bit ACCDE in the target 32-bit Access environment and the 64-bit ACCDE in the target 64-bit environment. Test forms, reports, linked tables, and features that call Windows APIs.
Use WPS Office for Compatible Office Documents
WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations in a familiar interface. Its Microsoft Office format support makes it easier to move everyday files between suites. WPS Office does not compile or run Access ACCDE databases, so use Microsoft Access for the database solution above.

Frequently Asked Questions
How do I check whether Access is 32-bit or 64-bit?
In Access, select File > Account > About Access. The About window displays the Office bitness.
Can one ACCDE file run in both 32-bit and 64-bit Access?
Do not rely on one compiled ACCDE for both environments. Create separate ACCDE files from the source ACCDB using Access with the bitness of each target environment.
Does adding PtrSafe fix every 64-bit VBA compatibility issue?
No. In the VBA editor, review each Declare statement and use appropriate types for pointers and handles, such as LongPtr. Also check references and any code that depends on bitness.
Do I need to change a shared Access back end for 64-bit Office?
A back end containing only data tables is generally unaffected by front-end ACCDE bitness. Check linked-table connections and any required drivers on each target system.
Can I recompile an ACCDE without the original ACCDB?
You need the editable source database to modify and recompile its VBA code. Ask the database developer for the ACCDB, then use Database Tools > Make ACCDE in each target Access environment.




