What you will notice is that when you run Data Sources (ODBC) from the administrative tools on Windows 7 x64, it doesn't have many of the drivers, such as the "SQL Server" driver. This is very important, and it does still exist, just in a different place. To find it open Windows Explorer and navigate to: C:\Windows\SysWOW64 in this directory (which stands for windows on windows) you will find an exe named "odbcad32.exe". This is where all the old 32 bit odbc drivers are located.

Now that you have found it, you can run this as an administrator either by loggin in as an administrator, or right clicking it and selecting "Run as administrator". Once you do, go to the "System DNS" tab, click "Add". Once you do this, pick the appropriate ODBC driver, and go through the following prompts as you would have in 32 bit Windows XP. Once finished make sure it is saved and exit the ODBC administration tool.

Find the appropriate program that you were trying to use that requires a 32 bit ODBC driver, and attempt to run it again. It should now run just fine. Note: if the program has a native 64 bit client, and has a native 64 bit odbc driver, you should stick with this as this will be the future of computing.

just thought it was interesting to note that each ODBC app creates entries that the other cannot see ...

the ODBC app under the Control Panel creates registry entries at "computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI"

the app under SysWOW64 creates entries at "computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI"

We are getting an error that says the setup routines for the Oracle in instantclient_11_2 ODBC driver could not be loaded to to system error code 193:

Any idea why this is happening?

If someone have any problems with ODBC connection to SQL Server or Oracle then I recommend you to look at this SQL Server and Oracle connection guides https://www.devart.com/odbc/sqlserver/docs/driver_configuration_and_conne.htm
https://www.devart.com/odbc/oracle/docs/driver_configuration_and_conne.htm