DevHeads.net

64 Bit versus 32 Bit

Good afternoon,
I’m not sure if you can help me, but maybe at least shed some light on things. I have a MS-Access database used by 6-7 different users. It mostly uses an MS-Access backend, but there are some connections to a PostgreSQL server as well. It was built with MS-Access 2010 32-bit because we still had a few 32-bit WinXP machines floating around. I used the PostgreSQL Unicode driver, version 9.01.01.00, and configured the connection with Window’s ODBC Data Source Administrator (32-bit). It has been working for several years.
Now that all of the computers have all been upgraded, some of the newer ones are getting Office 365 64-bit installed. When they open the database with a 64-bit version of Access, the ODBC connections fails. If I reinstall the 32-bit runtime version of MS-Access to open the file, everything works fine. However, I have tried installing the 64-bit PostgreSQL driver, version 11.00.00.00, but Access 64-bit still gives me the same error. The 64-bit ODBC connection test within the ODBC Data Source Administrator (64-bit) says that it is successful, but 64-bit Access still can’t open it. I don’t know if I can have both the 32-bit and the 64-bit drivers installed and setup with the same network connections or not. I’m not sure if there’s anything within the Access database file that’s directing it to use the 32-bit connection, but the 64-bit version of Access doesn’t like it, or what.
If you can shed any light on this I would appreciate it. Might be more of an Access-side question, but I thought I’d reach out just in case.

Thanks,

Cevin Moses
<a href="mailto: ... at imoses dot com"> ... at imoses dot com</a>
262-203-3895

Comments

Re: 64 Bit versus 32 Bit

By Cevin A Moses at 04/11/2019 - 17:45

Good afternoon,
I took a fresh Windows installation and installed just the 64-bit driver. The machine has Office 365 (64-bit) installed. I created the ODBC connection, which tested fine. Then I created a new database and tried to setup a linked table using that ODBC connection, but the connection is not listed. Here is a screen shot from the 64-bit machine:

And here is the same process on the 32-bit version of Access using the 32-bit ODBC driver.

As you can see, the connection is visible within Access in the 32-bit version, but the 64-bit version of Access cannot see the 64-bit ODBC connection as an option.

Might be a driver issue or an issue with Access, but it has nothing to do with my database file itself. At least I’ve ruled that part out.

Thanks,
Cevin

Good afternoon,
I’m not sure if you can help me, but maybe at least shed some light on things. I have a MS-Access database used by 6-7 different users. It mostly uses an MS-Access backend, but there are some connections to a PostgreSQL server as well. It was built with MS-Access 2010 32-bit because we still had a few 32-bit WinXP machines floating around. I used the PostgreSQL Unicode driver, version 9.01.01.00, and configured the connection with Window’s ODBC Data Source Administrator (32-bit). It has been working for several years.
Now that all of the computers have all been upgraded, some of the newer ones are getting Office 365 64-bit installed. When they open the database with a 64-bit version of Access, the ODBC connections fails. If I reinstall the 32-bit runtime version of MS-Access to open the file, everything works fine. However, I have tried installing the 64-bit PostgreSQL driver, version 11.00.00.00, but Access 64-bit still gives me the same error. The 64-bit ODBC connection test within the ODBC Data Source Administrator (64-bit) says that it is successful, but 64-bit Access still can’t open it. I don’t know if I can have both the 32-bit and the 64-bit drivers installed and setup with the same network connections or not. I’m not sure if there’s anything within the Access database file that’s directing it to use the 32-bit connection, but the 64-bit version of Access doesn’t like it, or what.
If you can shed any light on this I would appreciate it. Might be more of an Access-side question, but I thought I’d reach out just in case.

Thanks,

Cevin Moses
<a href="mailto: ... at imoses dot com"> ... at imoses dot com</a>
262-203-3895