Brian, The problem was a 32-bit application trying to use a DSN created in the default ODBC connection manager -- which in 64-bit Windows is the x64 version. To fix the problem, I had to use Start -> Run to manually select and execute the 32-bit connection manager -- located in "%systemdrive%\Windows\SysWoW64" (right where you said it would be). Doing so allowed me to create a DSN that worked perfectly with my 32-bit DBI application.
-Brian -----Original Message----- From: Brian Manning [mailto:[email protected]] Sent: Monday, May 11, 2009 11:38 To: Brian H. Oak Cc: [email protected] Subject: Re: DBD::ODBC and 64-bit Windows On Mon, May 11, 2009 at 9:22 AM, Brian H. Oak <[email protected]> wrote: > Brian, > > It took quite a while before I was able to again gain access to the server in > question...but when I did, your instructions solved the problem. I just > wanted to send you a delayed but very sincere "THANK YOU!" Just so others who hit this problem can fix it, what was the actual problem and fix? Did you create a 64-bit ODBC DSN and you're using 32-bit ActiveState (or some other 32-bit application), or the other way around, you created a 32-bit ODBC DSN for a 64 bit app? Thanks, Brian
