Fix an Access Database That Opens on One Computer but Not Another
Question details
A user needs a VB.NET application to open a password-protected Access database on a new notebook.

- Product
- Microsoft Access Database Engine and Office 2016
- Device & OS
- not provided
- Scenario
- A VB.NET application and its Access database were moved from older computers to a new notebook with Office 2016.
- Observed behavior
- The application works on the older computers but reports an unrecognized or corrupt database on the new notebook.
Check the provider name in the application's connection string and determine whether the running application is 32-bit or 64-bit. You will also need the database password and access to the database file on the new notebook.
Install an Access Database Engine That Matches the Application
Use this solution when the new notebook may have the wrong ACE provider or a provider with incompatible bitness.
Open the application's configuration or source code and inspect its connection string. Note whether it specifies Provider=Microsoft.ACE.OLEDB.12.0.
In Visual Studio, open the project's properties and check its platform target and Prefer 32-bit setting. For a running application, you can also inspect its process platform in Task Manager's Details tab.
Download a Microsoft Access Database Engine redistributable from Microsoft that provides the required ACE provider, and choose the 32-bit or 64-bit edition to match the application process. For an ACE 12.0 connection, the Access Database Engine 2010 Redistributable was the version used in the reported fix.
Restart the VB.NET application and open the database again using the existing connection settings.

Check the Database File and Its Location
Use these checks if the matching provider is installed but the database still cannot be opened.
Work With Office Files in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface for working with Office documents and spreadsheets. Its format compatibility helps you move everyday files between Microsoft Office and WPS Office. It does not replace the Access Database Engine or fix an ACE provider error.

Frequently Asked Questions
Does the Access Database Engine need to match Office or the application?
The provider used by the VB.NET application must match the application's process bitness. Check the platform target in Visual Studio or inspect the running process in Task Manager. Also check Microsoft's installation guidance for conflicts with the installed Office edition.
How do I know which ACE provider the application uses?
Look in the application's configuration file or source code for its connection string. A provider entry such as Microsoft.ACE.OLEDB.12.0 identifies the requested ACE provider.
Does an unrecognized database error mean the file is corrupt?
Not necessarily. A missing or incompatible provider can also prevent the application from opening the file. If Access is available, try File > Open with the same database and password to help distinguish a file issue from an application connection issue.
Can WPS Office fix the Access provider error?
No. The VB.NET application needs a compatible Microsoft Access Database Engine provider. WPS Office can work with spreadsheet data exported from Access, but it does not replace the ACE provider.




