Access 365 Pro Plus 64 bit and Oracle 11g 32 bit ODBC driver

Question

Access 365 Pro Plus 64 bit and Oracle 11g 32 bit ODBC driver

Keeping, Tim (DEM) 1

On Win 10 64 bit too. No problems with Office 2016, but IT just upgraded us to 365.

ODBC 32 bit has a User DSN entry using an Oracle 11g 32 bit driver, and it tests OK.

ODBC 64 bit also lists the same named User DSN entry but

the Oracle 32 bit driver does not appear in the Driver tab
The Remove and Configuration buttons are greyed out so I cannot test

When I try to use this DSN in Access 365 64 bit it complains about mismatched architecture.

DB admin thinks it should not be a problem and claims his 64 bit Access is using the 32 bit driver.

The general consensus on the internet is you cannot cross Access and drivers of mismatching bits. The error sounds exactly like that. I cannot see the driver in 64 bit ODBC Administrator so that makes sense.

A simple question - does 64 bit Access need a 64 bit ODBC driver?

Keeping, Tim (DEM) 1 Reputation point

2021-01-20T23:18:31.38+00:00
(I cannot see the edit button)

More questions

Which ODBC is Access 365 "seeing"? The 32 or 64 bit list?

If ODBC is automatically replicating 32 bits DSN names into the 64 bit list, what does this mean? Is Win 10 "bridging" and so 32 ODBC bit drivers can work for 64 bit apps?

1 answer

Your answer

Keeping, Tim (DEM) 1 Reputation point

2021-01-20T23:18:31.38+00:00

(I cannot see the edit button)

More questions

Which ODBC is Access 365 "seeing"? The 32 or 64 bit list?

If ODBC is automatically replicating 32 bits DSN names into the 64 bit list, what does this mean? Is Win 10 "bridging" and so 32 ODBC bit drivers can work for 64 bit apps?

Answer 1

Erin Ding-MSFT 4,476

@Keeping, Tim (DEM)

Generally, we suggest to match bits between ODBC driver and Access.

You could try to go to %systemdrive%\Windows\SysWoW64 to use the 32-bit odbcad32.exe to configure the DSN.

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Keeping, Tim (DEM) 1 Reputation point

2021-01-20T23:16:22.823+00:00
Thanks eringing-msft.

I can but the problem is that 32 bit is the only ODBC allowing configuration, so I cannot tell if 64 bit ODBC is the problem or Access 365. Since Access 365 is the only change I assume that is the problem.

The 32 bit driver only appears as an option %systemdrive%\Windows\SysWoW64\odbcda32.exe.

So I can make a User DSN in odbc 32 bit, and the test connection works.

The same name then appears in the DSN list for ODBC 64 bit admin tool ( the one oddly named odbcad32.exe but in %systemdrive%\Windows\system32 instead). But it cannot be removed or configured so I cannot test.

Access 365 shows the DSN name under Machine DSN list but then complains of a mismatch after pressing OK.

This raises the questions

Which ODBC is Access 365 "seeing"?

If ODBC is automatically replicating 32 bits DSN names into the 64 bit list, what does this mean? Is Win 10 "bridging" and so 32 ODBC bit drivers can work for 64 bit apps?

Share via

Access 365 Pro Plus 64 bit and Oracle 11g 32 bit ODBC driver

1 answer

Your answer