Troubleshooting

Setting up an Oracle ODBC Driver and Data Source requires more steps than the Microsoft SQL Server database setup. This article explains the steps including tnsnames.ora configuration. Connecting to an Oracle database via and ODBC driver requires the following steps. Hi, I just downloaded, burnt and installed the new windows 7 RC, x64, on my alu 24' iMac. Maybe I should have just taken the 32 bit version as it has only 2 gigs of ram, but I don't feel like wasting more time and another dvd on getting the 32 bit one. Connector/ODBC is a standardized database driver for Windows, Linux, Mac OS X, and Unix platforms. Online Documentation: MySQL Connector/ODBC Installation Instructions, Documentation and Change History. Connector/ODBC is a standardized database driver for Windows, Linux, Mac OS X, and Unix platforms. Online Documentation: MySQL Connector/ODBC Installation Instructions, Documentation. Important: As of August 2016, Excel 2016 for the Mac was updated from 32-bit software to 64-bit software. To see if you have this update, click the Excel menu > About Excel. If you have version 15.25 or later, you have the 64-bit version.

Just trying to find the Microsoft driver to install the ODBC driver excel 32 bit on a Windows 7 and Office 2013 professional 64 bit. Edited by Living Large in LV Thursday, August 18, 2016 11:40 PM Thursday, August 18, 2016 11:32 PM. Msi pc54g3 wireless 11g pci card drivers for mac.

Problem

IBM iSeries Access for Windows provides both a 32-bit and 64-bit ODBC driver. This document contains information related to the 64-bit version of the ODBC driver.

Resolving The Problem

IBM iSeries Access for Windows provides both a 32-bit and 64-bit ODBC driver. The 64-bit ODBC driver is automatically installed along with the 32-bit ODBC driver when running under a 64-bit version of Microsoft Windows. ODBC applications running in 64-bit versions of Windows will automatically use the appropriate ODBC driver, depending on whether the application was compiled as 32-bit or 64-bit.
Microsoft provides the following versions of the ODBC Administrator: 32-bit and 64-bit. Both versions are named odbcad32.exe (there is no odbcad64.exe). Both versions can be accessed from the iSeries Access for Windows folder.
64-bit Windows has the familiar C:WindowsSystem32 directory, and it also has a C:WindowsSysWOW64 directory that serves a similar function as a repository for system files. That seems straight-forward. One would think that the 32-bit system files would go in the System32 directory and the 64-bit system files would go in the SysWOW64 directory. That is not the way it works. Some things in 64-bit Windows are the opposite of what you would expect. The windowssystem32odbcad32.exe is really the 64-bit ODBC Administrator. The windowsSysWOW64odbcad32.exe is the 32-bit ODBC Administrator.
Note: All available information indicates that all 64-bit files are stored in System32 and all 32-bit files are stored in SysWOW64. This does not apply just to ODBC related files.
Similarly, the 64-bit ODBC driver that is installed with iSeries Access for Windows on a 64-bit Windows PC is windowssystem32cwbodbc.dll and the 32-bit driver is windowsSysWOW64cwbodbc.dll. The driver name in both cases is iSeries Access ODBC Driver. The version of the driver manager (odbc32.dll) determines to which driver the ODBC calls get routed.
When running on 64-bit Windows, User DSNs will work with either driver. System DSNs that are created with 64-bit ODBC Administrator will only work with the 64-bit Driver. System DSNs that are created with the 32-bit ODBC Administrator will only work with the 32-bit driver. The best way to ensure that the correct DSN is created is to always use the ODBC Administration shortcuts that are created in the iSeries Access for Windows Program group because those shortcuts are properly labeled as either 32-bit or 64-bit.
The version information for the iSeries Access for Windows 64-bit ODBC contains the number 64, so it is easily identifiable. The format for the version information for Windows 32-bit or 64-bit iSeries Access for Windows ODBC driver is: aa.bb.dd.dd, where aa corresponds with the version of iSeries Access for Windows (V5R3 is 10, V5R4 is 11, and so on), bb is 0 (32-bit) or 64 (64-bit), cc is the service pack (SP) version (SP1 is 1, SP2 is 2, and so on), dd is a special fix version number (always 0 except in cases where a particular patch has been provided).
Restrictions of the 64-bit iSeries Access for Windows ODBC Driver:
Microsoft Transaction Server (MTS) is not supported on the 64-bit iSeries Access for Windows ODBC driver. For additional Information about MTS, refer to the link Use Microsoft Transaction Server (MTS) in the iSeries V5R4 InfoCenter.
Prior to V6R1 System i Access for Windows, only the Intel Itanium 64-bit processor family is supported for ODBC SSL connections. At V6R1 System i Access for Windows, support was added to include ODBC SSL connection support for the AMD 64-bit processor family. This restriction is documented in the V5R4 Information Center.
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzaij/rzaijwhatsnew.htm
Versions of iSeries Access for Windows that are supported when running on 64-bit Windows:
iSeries Access for Windows V5R4M0 and iSeries Access for Windows V5R3M0 with service pack PTF SI17742 (or later) are supported when running on 64-bit Windows. Client Access Express V5R1M0 with Service Pack SI11806 might install on 64-bit Windows and iSeries Access for Windows V5R2M0 with Service Pack SI18400 (or later) usually will install on 64-bit Windows. Some functions might work with the earlier versions, but no support is provided for these environments. It is recommended to install the V5R3M0 client using a merged PTF installation image rather than installing the base V5R3 client and then installing the service pack. Refer to the readmesp.txt file that comes with the service pack from the FTP server for instructions on how to create a merged installation image:
ftp://ftp.software.ibm.com/as400/products/clientaccess/win32/v5r3m0/servicepack/si24723/readmesp.txt
Refer to the iSeries Access for Windows home page section titled Microsoft Windows Operating Systems and iSeries Access.

Internal Use Only

IBM ISERIES CLIENT ACCESS EXP (5722XE100)

I’m running 64-bit Windows 7 Pro SP1.

I needed the 64-bit odbc drivers for Access databases and naturally thought that these would be installed if I upgraded from 32-bit Office 2010 to 64-bit Office 2016.

Win 7 64 Bit Odbc Driver For Machine

Windows 7 64-bit Odbc

The process of making that upgrade has been a nightmare in its own right. (It has taken me the best part of a week). The Access version installed is 16.0.4266.1003 64-bit. Imagine my despair then to find that, having 64-bit Office 2016 installed, did not result in the 64-bit drivers being installed.

I therefore downloaded and tried to install the 64-bit Access 2016 runtime. And this is what happened…

Windows 64-bit Odbc Drivers

We're sorry, Microsoft Office installer encountered a problem because you have these Click-to-Run installer based Office programs installed on your computer.

Microsoft Office Professional Plus 2016 - en-us

Windows Installer and Click-to-Run editions of Office programs don't get along for this version, so you can only have one type installed at a time. Please try installing the Click-to_run edition of Office instead, or uninstall your other Click-to-Run based Office programs and try this installation again.

So, I thought I’d try to install the 64-bit Access 2013 runtime, and this is what happened…

Microsoft Access Runtime 2013 encountered an error during setup.

Microsoft Drivers For Windows 7 64 Bit

So, just what am I supposed to do to get the 64-bit Access ODBC drivers installed????