'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix ACE.OLEDB.12.0 Provider Not Registered in Visual Studio 2019
Question details
The user needs to resolve an OLEDB provider registration error when attempting to connect to a Microsoft Access database through Visual Studio 2019.
- Product
- Visual Studio 2019
- Device & OS
- Windows
- Scenario
- Developing an application in Visual Studio 2019 and connecting it to a Microsoft Access database.
- Observed behavior
- Visual Studio 2019 throws an error stating that the Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine.
Check whether your Visual Studio 2019 project is currently configured to build as a 32-bit (x86) or 64-bit (x64) application before downloading the database engine.
Install the 32-bit Microsoft Access Database Engine
Since Visual Studio 2019 is a 32-bit application, installing the 32-bit version of the Access Database Engine aligns the architectures and resolves the provider error.
The most common cause of the ACE.OLEDB.12.0 provider error is a mismatch between the bitness of the Visual Studio application and the installed OLEDB provider. Installing the 32-bit engine explicitly provides the files Visual Studio 2019 needs during development.
Navigate to the official Microsoft download page for the Microsoft Access Database Engine 2010 or 2016 Redistributable.
Click Download and explicitly select the 32-bit installation file (typically named AccessDatabaseEngine.exe without the _X64 suffix).
Execute the downloaded file and follow the standard installation wizard steps to complete the setup.
Close Visual Studio 2019 entirely. Reopen your project, go to the Build menu, click Rebuild Solution, and run the application again.
Match Project Architecture to the Installed OLEDB Provider
If you already have the 64-bit Access Database Engine installed on your machine, you can fix the issue by configuring your project to build specifically for 64-bit.
Seek Further Help in Microsoft Q&A Forums
If architectural adjustments do not resolve the error, the issue may involve deeper system configuration problems that require community troubleshooting.
Need a Lightweight Office Suite for Your Data Work?
While WPS Office does not resolve Visual Studio compilation or OLEDB provider errors, it provides a powerful, free, and lightweight alternative to Microsoft Office for managing spreadsheet data, CSVs, and documents.
- 1. Download WPS Office: Visit the official WPS website and click the free download button to get the installer.
- 2. Install the application: Run the setup file and follow the simple on-screen prompts to install the lightweight office suite.
- 3. Manage your data: Launch WPS Spreadsheets to seamlessly open, edit, and format your exported database files or Excel documents.
Frequently Asked Questions
Why does the ACE.OLEDB.12.0 error occur specifically in Visual Studio 2019?
Visual Studio 2019 is a 32-bit application. When it tries to interact with data connections during design time or debug mode, it requires the 32-bit OLEDB provider. If only the 64-bit engine is installed, Visual Studio cannot find the necessary 32-bit registry keys.
Can I install both 32-bit and 64-bit Microsoft Access Database Engines on the same machine?
By default, Microsoft prevents installing both versions side-by-side. However, you can bypass this by opening the Command Prompt, navigating to the installer's directory, and running the executable with the '/passive' flag (e.g., AccessDatabaseEngine.exe /passive).
Does changing the Platform Target to 'Any CPU' fix the OLEDB provider error?
Setting the target to 'Any CPU' might cause the application to run as 64-bit on a 64-bit OS but as 32-bit in the Visual Studio debugger. It is highly recommended to explicitly target 'x86' or 'x64' depending on which Access Database Engine is installed.
