ODBC DSN with 64-bit SQL Server

I don't know what platform he is running my software on (and I can't test or verify the problem).  I do know that every other part of the program runs perfectly and that even this part works fine when the "Use custom connection string" option is selected and the other (non-DSN) string is used.  So I think I can rule out any oddities about my 32-bit software being installed wrong on his 64-bit platform.

I got a hint from somewhere about the 64-bit vs. 32-bit ODBC Manager, but I could not verify it or get additional info.  I'm hoping that someone has direct experience with this.

-- Dan

I think I've found the simplest solution.  It appears that there are two programs named
       ODBCad32.Exe
(which handles the ODBC Data Source Administrator dialogs).  On a 64-bit client, the one that comes up normally only displays the 64-bit database Drivers (and apparently the old/reliable standard "DSN=" syntax is not supported -- or something -- by the 64-bit ODBC Administrator or the 64-bit driver).

The solution recommended to me is to manually run the 32-bit version of the ODBC Administrator.   It can usually be found at:

      C:\Windows\sysWOW64\ODBCad32.Exe
                           ========

And then set up the DSN as usual.  According to what I read, that will create a 32-bit DSN that my 32-bit program should be able to access normally.

I am not able to test or verify this, and I'd really appreciate it if someone running 64-bit Windows would check it out (verify the file location and functionality) before I pass the info on to my client and update the documentation.

Thanks!
-- Dan

Hmm, I've never heard of that technique.  Logically it makes sense that it could work, otherwise why would Microsoft bother to leave it there?  I have 64bit systems at work that I actually want to try this with (I've had similiar problems) but I won't be able to do it until Monday.  (I'm at home today)

From that second link, the authoritative post:

     On 64 bit Windows you have seperate[sic] 32 bit and 64 bit ODBC worlds.
     There is no thunking between 32 and 64 bit components as there was
     between 16 and  32 bit. To work with 32 bit drivers you need to run the
     32 bit ODBC administrator C:\WINDOWS\SysWOW64\odbcad32.exe

I've asked the client to try this out.  I'll let you all know what happens.

My client indicated that locating and using the 32-bit version of the ODBC Administrator allowed him to create a "normal" DSN which which let my program use a standard connection string (DSN+ etc).

I consider this a flaw in Microsoft's implementation of their 64-bit SQL Server drivers and/or a flaw in their handling of ODBC Administration in the 64-bit OS.  In any case, it's good to know that there is a workaround

Thanks for your help.
-- Dan