Windows 10: Using NTFS Mount as an ODBC Data Source

We have a Windows 10 Pro PC running on a VM that has a mounted NFTS drive, just using the anon switch to not require credentials. The drive letter is Z and net use shows it as an NFS Network drive mount. We can browse and interact with it just fine in explorer.However, one of our apps requires a 32-bit ODBC connection to that mounted drive. But I can't get the ODBC connection to set up to save my life. Steps I followed are below:1. Open 32-bit ODBC Data Source Administrator2. Click Add under User DSN3. Select MS Text Driver as the driver4. Click finish and add the DSN name5. Unclick Use Curren

:)

 

New data source ODBC driver could not be loaded due to system error 126

Hello,

I have an error when i want to add User DSN in ODBC data administrator 32 bit after clicking the related driver..

"The setup routines for the CSI RBM 4.02 ODBC Driver ODBC Driver could not be loaded due to system error code 126: The specified module could not be found. (C:\Windows\system32\mt40odbc.dll)."

1. I have already installed the driver and already listed in drivers tab ODBC Data source administrator 32 bit (only in 32-bit).
   
2. The file specified above (C:\Windows\system32\mt40odbc.dll) is already EXIST.
   

I used windows 64-bit and the driver was 32 bit.

Gracias

 

ODBC Data Sources (32-bit and 64-bit) seem to be the same

There are two applications under Windows Administrative Tools called ODBC Data Sources (32-bit) and ODBC Data Sources (64-bit). But their shortcuts both point to the same file: %windir%\syswow64\odbcad32.exe. I would expect the 64-bit file to have a name
like odbcad64.exe. Why is the same file used for both 32-bit and 64-bit?

BTW, Windows topics (selected below) should have an "Other" selection when the listed selections don't seem to fit the topic being questioned about.

***moved the thread to the nearest category by query.***

 

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.