Data Import & Export

Find the Correct Microsoft 365 Excel ODBC Connection String

Elise WilliamsElise Williams Nov 13, 2026 868 views

Question details

Find the correct connection-string value for an application that accesses an Excel workbook using drivers already installed in an Office 365 environment.

Find the Correct Microsoft 365 Excel ODBC Connection String
Product
Microsoft 365 Excel and the installed Excel ODBC driver
Device & OS
not provided
Scenario
An application needs to connect to an Excel file on an enterprise computer where the user cannot install or replace drivers.
Observed behavior
The connection must use the registered driver, support the workbook format, and match the application's 32-bit or 64-bit architecture. ODBCJT32.DLL indicates a 32-bit driver environment.
Before you start

Check whether the application is 32-bit or 64-bit, and identify the workbook's extension and full file path. Inspect the drivers already registered on the computer where the application runs; the Office 365 product name alone does not determine the connection string.

Solution 1Recommended

Build a DSN-less connection string with the registered Excel ODBC driver

Use this approach when the application accepts an ODBC connection string and you must rely on existing enterprise drivers.

ODBC connection strings use a Driver or DSN value. Jet and ACE Provider strings belong to OLE DB and are not interchangeable with ODBC strings. First confirm which connection interface your application expects.

1
Open the matching ODBC administrator

On Windows, open Start and search for ODBC Data Sources (32-bit) or ODBC Data Sources (64-bit), matching the application's architecture. On 64-bit Windows, %windir%\SysWOW64\odbcad32.exe manages 32-bit drivers, while %windir%\System32\odbcad32.exe manages 64-bit drivers.

2
Copy the registered driver name

Select the Drivers tab and locate an Excel driver that supports your workbook's extension. Copy its name exactly as displayed. If only a legacy driver supporting .xls files is listed, do not assume it supports .xlsx files.

3
Enter the workbook connection string

In the application's ODBC connection setting, use the template Driver={EXACT REGISTERED DRIVER NAME};DBQ=C:\Data\Workbook.xlsx;. Replace the driver placeholder with the name from the Drivers tab and replace the path with your actual workbook path. Confirm DBQ and any additional options in the installed driver's documentation.

4
Test from the application's environment

Run the application's connection test or a small ODBC test program with the same architecture and account as the production application. Confirm that the account can access the workbook path and that the driver can read the workbook format.

Build a DSN-less connection string with the registered Excel ODBC driver
A 32-bit driver requires a 32-bit application: ODBCJT32.DLL indicates a 32-bit driver environment. A 64-bit application cannot load that driver directly, even if Windows itself is 64-bit. If no compatible driver is available, ask the enterprise administrator about approved options rather than substituting an arbitrary ACE or Jet string.
Free Microsoft Office alternative

Open and Review Excel Workbooks with WPS Spreadsheet

WPS Office is a free, lightweight alternative for opening and reviewing Excel workbooks, with a familiar spreadsheet interface and Microsoft Office format compatibility for easy migration. It does not install or repair Microsoft's Excel ODBC drivers or resolve application-driver architecture mismatches.

Open and review workbook data before testing an external application's connection.Work with Microsoft Excel .xls and .xlsx formats.Use a familiar spreadsheet interface for everyday editing.Move existing Office documents into a lightweight productivity suite.
QA img-9

Frequently Asked Questions

Is there one Excel ODBC connection string for every Office 365 installation?

No. Open the matching ODBC Data Source Administrator and check the Drivers tab. The correct string depends on the registered driver, its supported workbook formats, and the application's architecture—not just the Office version.

Should I use Provider=Microsoft.ACE.OLEDB in an ODBC connection string?

No. Provider=Microsoft.ACE.OLEDB identifies an OLE DB provider. If your application uses ODBC, configure Driver={registered driver name};DBQ=workbook path; or DSN=your data source name;. Use an ACE provider string only when the application explicitly supports OLE DB and the matching provider is installed.

Why is an installed Excel driver missing from the driver list?

You may be viewing the administrator for the wrong architecture. On 64-bit Windows, open ODBC Data Sources (32-bit) for a 32-bit application or ODBC Data Sources (64-bit) for a 64-bit application, then check the Drivers tab again.

What can I do if I am not allowed to install a different driver?

Use the installed driver's exact registered name and a supported workbook format. If its architecture does not match the application, ask whether the application can run in the matching architecture. Otherwise, contact the enterprise administrator for an approved access method; changing the connection-string text cannot fix a missing or incompatible driver.

Can WPS Office fix an Excel ODBC driver connection error?

No. WPS Spreadsheet can open and review compatible Excel workbooks, but it does not repair Microsoft's ODBC driver registration. Diagnose the connection in the matching ODBC Data Source Administrator and test it from the application that will access the file.