Windows 10: ODBC driver inserted from registry key does not show up in Source Administration

I have exported an existing PostgreSQL ODBC driver 64 bit entry from the registry at Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INIAnd modified the name of the driver name.The original was[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\PostgreSQL ODBC DriverUNICODE]"APILevel"="1""ConnectFunctions"="YYN""Driver"="C:\\Program Files\\PostgreSQL\\psqlODBC\\bin\\psqlodbc30a.dll""DriverODBCVer"="13.00.0000""FileUsage"="0""Setup"="C:\\Program Files\\PostgreSQL\\psqlODBC\\bin\\psqlodbc30a.dll""SQLLevel"="1"and my modified driver is[HKEY_LOCAL_MACHINE\SOFTWARE\

:)

 

Suspect configuration of ODBC


I suspect that something is not correct concerning the configuration of ODBC. The Control Panel shows the two entries for this software as it should for a 64 bit system and when you drill down to General under Properties it shows the correct shortcuts for both versions, i.e. system 32 for the 64 bit and SySwow64 for the 32 bit.

When you open up both versions to look at the Administrators, the data appears to be identical for both in some cases. User DSN, System DSN (empty), File DSN, Tracing and About appear to be the same in both. However, in User Data Sources both sets of files are flagged as 32 bit platform and in About all the ODBC Core Components for both versions are pointing to system32 location which is the 64 bit.

For the Drivers tab the 32 bit version is fully populated including SQL Server, most having a version no. of 10.00.1493.00. For the 64 bit version the only entry is SQL Server with the same version.

The same goes for Connection Pooling. The 32 bit version is populated including a SQL Server whereas the 64 bit version only has SQL Server.

Reading various posts online I would expect the 32 bit version to refer to syswow64 files and the 64 bit be populated with the system32 ones if they were there, which they are not.

I also have found the following-:
https://blogs.msdn.microsoft.com/dat...-odbcad32-exe/
Towards the bottom of the first paragraph it says that on a 64 bit system the 64 bit drivers are held at a certain registry location. The registry has the full path but under ODBC Drivers there is only the one entry for the SQLServer which bears out what the Drivers tab is saying above. The 32 bit drivers are there, again confirming the Drivers tab. In the screenshot it shows a typical 64bit system for 64 bit drivers, that data is not in mine.

Below the screenshot it talks about certain registry keys be set to value not set. On my system under 64 bit system and 64 bit drivers, items 1 and 2 are as I have them. For the 32 bit drivers items 1 and 2 again are as per post. However, in both locations ODBCINST.INI and ODBC the 32 bit drivers are fully populated.

To me the 32 bit drivers are in the right place in the registry but not when you look in the Administrators. As for the 64 bit drivers, they appear not to be in the registry nor in the Administrator.

Incidentally, the SQLServer for both versions in the ODBC registry, point to system 32.

This system is an upgrade from Windows 7. Am I wrong in my assumptions or I have missed something, guidance appreciated. If I am correct, how does one resolve this?

 

File DSN are slow to scan when opening ODBC Data Source Administrator

*Sigh* I swear I spent an hour googling. I figured it out myself. To describe the symptom again:

• If you open the ODBC Data Sources Administrator, and it is very slow to load the File DSN tab (e.g., a few minutes), and/or if when you select an ODBC export from Microsoft Access, and Access becomes unresponsive for a few minutes before opening the ODBC
  connection window, then...
• Your File DSN directory may not be set. The default is a location in Program Files; mine was scanning my Documents directory, which is huge. I don't know why it was set that way. Anyway, I set it to an empty local folder (I never use File DSN), and now
  it opens lickity-split.

 

Windows 10 unable to add Visual FoxPro ODBC driver

I am attempting to add the Visual FoxPro ODBC driver to my list of active data sources, but am unable to do so.

I have installed the latest driver downloaded directly from microsoft, and I have found the driver .dll file in windows explorer. However, when I attempt to add the data connection via ODBC Data Sources (32-bit), the driver does not come up in the available list.

I checked the list in ODBC Data Sources (64-bit), just to make sure it was not listed there. I am aware that the FoxPro ODBC driver is 32-bit only.




What next steps should I take in troubleshooting this issue? I've been googling for over two hours now, with no new developments. Thanks.