Windows 10: Is there any way to communicate with 32 bit odbc DSN from my application hosted in IIS...

Is there any way to communicate with 32 bit odbc DSN from my application hosted in IIS 10.0.1904?

:)

 

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

When I trigger the opening of the 32-bit or 64-bit ODBC Data Source Administrator, and select File DSN, it takes forever to show the tab.

I see this when I export a table from Microsoft Access to a SQL Server db. That I can discern, this is because the first tab the administrator opens when triggered from Access is the File DSN tab.

There's lots of ways around this relative to the specific issue I have; but, how do I stop the ODBC administrator from taking so long to display File DSNs?

 

ODBC Registry settings are not reflected in UI - ODBC Database administrator(32-bit)

I am using Windows Server 2019 version 1809 OS Build 17763.1158. I want to enable encryption for ODBC DSN connection So I am calling this command "C:\Windows\SysWOW64\odbcconf.exe /A {CONFIGSYSDSN "ODBC Driver 17 for SQL Server" "DSN=MVF|Server=%SDX_DBSERVER%|Encrypt=yes|TrustServerCertificate=yes"}" from the script file (.bat file).

Registry settings are updated properly under "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBC.INI\MYDatasource" but when I launch ODBC Database administrator(32-bit) and selected my data source and clicked on configure -> Next -> Next->Next check

 

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.