Office Compatibility Issues

Fix Access Runtime Errors in Microsoft 365 by Comparing ODBC Drivers

Olivia MillerOlivia Miller Nov 14, 2026 868 views

Question details

Identify why an application fails in Microsoft 365 Access Runtime but works in Access Runtime 2016.

Fix Microsoft 365 Access Runtime Errors by Comparing ODBC Drivers
Product
Microsoft 365 Access Runtime and Access Runtime 2016
Device & OS
not provided
Scenario
An application is run with two versions of Access Runtime and may depend on ODBC drivers or other database components.
Observed behavior
The application produces an error in Microsoft 365 Access Runtime but runs correctly in Access Runtime 2016.
Before you start

Record the exact error message and identify the database connection that triggers it. If possible, inspect both runtime environments so you can compare their drivers, architecture, and connection settings.

Solution 1Recommended

Compare ODBC drivers and runtime architecture

Use this comparison to find driver or bitness differences that may explain the error.

1
Identify the runtime architecture

On each Windows installation, open Task Manager and check the Access process architecture in the Details view. Record whether each runtime is 32-bit or 64-bit.

2
Compare installed ODBC drivers

Open the ODBC Data Source Administrator matching the runtime architecture: run %windir%\SysWOW64\odbcad32.exe for 32-bit or %windir%\System32\odbcad32.exe for 64-bit. On the Drivers tab, compare driver names and versions in both environments.

3
Check data sources and connection strings

In the matching ODBC Data Source Administrator, compare the User DSN and System DSN settings used by the application. Also inspect its connection string or configuration file for the driver name, server, database, and authentication settings.

4
Test a matching driver

Where compatible, install or select the same ODBC driver and architecture used by the working environment, update the application's DSN or connection string if needed, and run the application again.

Compare ODBC drivers and runtime architecture
Match the application's architecture: A 32-bit application needs a 32-bit ODBC driver, while a 64-bit application needs a 64-bit driver. Driver availability and compatibility may differ between environments.
Free Microsoft Office alternative

Work with Office documents in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for working with Office documents and moving between suites. It does not fix Access Runtime errors or run Access database applications.

Create and edit documents, spreadsheets, and presentations in a familiar interfaceOpen and save common Microsoft Office formats, including DOCX, XLSX, and PPTXUse a free, lightweight suite for everyday office workReview spreadsheet exports from database applications in WPS Spreadsheets
microsoft office alternative - wps office

Frequently Asked Questions

Why does the application work in Access Runtime 2016 but fail in Microsoft 365 Access Runtime?

The environments may use different ODBC drivers, runtime architectures, connection strings, or database components. Compare these settings and use the exact error message to narrow down the cause.

How do I check which ODBC drivers are installed?

On Windows, open the ODBC Data Source Administrator for the application's architecture and select the Drivers tab. Run %windir%\SysWOW64\odbcad32.exe for 32-bit drivers or %windir%\System32\odbcad32.exe for 64-bit drivers.

Does my ODBC driver need to match Access Runtime bitness?

Yes. A 32-bit Access application needs a 32-bit ODBC driver, and a 64-bit application needs a 64-bit driver. Check the driver in the corresponding ODBC Data Source Administrator.

Can WPS Office run my Access Runtime application?

No. WPS Office does not run Access database applications or replace Access Runtime. It can open common Office files and spreadsheet exports, but the Access Runtime issue must be resolved in the Microsoft environment.