VBA & Macro Problems

How to Connect 32-Bit Access Data with 64-Bit Excel VBA

Maira MehtabMaira Mehtab Nov 2, 2026 870 views

Question details

Users need to interact with a 32-bit Access database using VBA macros in a 64-bit version of Excel, but face connection failures due to architecture mismatch.

How to Use 32-Bit Access Data with 64-Bit Excel VBA
Product
Excel, Access
Device & OS
not provided
Scenario
Running existing Excel VBA macros that connect to an Access database (.mdb or .accdb) after upgrading Microsoft Office from 32-bit to 64-bit.
Observed behavior
The VBA macro stops working and fails to automate the database, throwing errors such as Error 3024 when using methods like Workspaces(0).OpenDatabase.
Before you start

Verify the exact bitness of your Excel application by navigating to File > Account > About Excel to confirm it is running the 64-bit version.

Solution 1Recommended

Install Matching 64-Bit Database Engine Drivers

The most direct method to resolve automation errors is to ensure your database drivers match the 64-bit architecture of your Excel application.

Components of different bitness cannot be automated directly. By installing the 64-bit Access Database Engine, your 64-bit Excel VBA code can successfully communicate with the database file.

1
Download the 64-bit Driver

Visit the official Microsoft download center and search for the 'Microsoft Access Database Engine 2016 Redistributable'. Click Download and explicitly select the 64-bit executable (AccessDatabaseEngine_X64.exe).

2
Install the Database Engine

Run the downloaded executable file and follow the on-screen installation prompts to install the 64-bit drivers on your system.

3
Update the VBA Connection String

Open your Excel workbook, press ALT + F11 to open the VBA Editor, and locate your database connection string. Change the old 32-bit provider (e.g., Microsoft.Jet.OLEDB.4.0) to the 64-bit provider (Provider=Microsoft.ACE.OLEDB.12.0; or 16.0).

Install Matching 64-Bit Database Engine Drivers
Updating from MDB files: If you are connecting to older .mdb files, switching to the newer ACE OLEDB provider is required because the Jet OLEDB provider is not available in 64-bit.
Free Microsoft Office alternative

Try WPS Office for Seamless Macro Compatibility

If you frequently encounter compatibility issues or complex driver requirements after Office updates, consider switching to WPS Office. It provides robust VBA support, high compatibility with Excel macros, and a lightweight installation to simplify your workflow.

  1. 1. Download the Installer: Navigate to the official WPS Office website and click the Free Download button.
  2. 2. Install WPS Office: Run the downloaded installer file and follow the quick setup instructions.
  3. 3. Open Your Macro Workbook: Launch WPS Spreadsheet and open your .xlsm file to seamlessly run your VBA code.
Highly compatible with Microsoft Excel formats (.xlsx, .xlsm, .csv)Built-in robust VBA editor for running and editing legacy macrosLightweight installation with significantly faster load timesFree to use with a familiar, easy-to-navigate interface
microsoft office alternative - wps office

Frequently Asked Questions

Why does Error 3024 occur when automating Access from Excel?

Error 3024 typically occurs when the database file cannot be found, or when there is a mismatch between the bitness of the database engine (like a 32-bit driver) and the calling application (64-bit Excel).

Can a 64-bit Excel application use the 32-bit Jet OLEDB provider?

No, 64-bit applications cannot utilize 32-bit OLEDB providers. You must install the 64-bit ACE OLEDB provider (Access Database Engine) to connect to databases from a 64-bit installation of Excel.

How do I format my VBA connection string for 64-bit Office?

You need to replace the older Jet provider with the ACE provider. Use 'Provider=Microsoft.ACE.OLEDB.12.0;' or 'Provider=Microsoft.ACE.OLEDB.16.0;' in your VBA connection string after installing the 64-bit Access Database Engine.