All, Thank you all for your helpful advise. I got it working on the server.
What was screwing me up was that the server already had a 32-bit client installed. So I was never going to get a 64-bit client working with 64-bit perl. I de-installed the 64-bit ODBC driver and 64-bit perl, and installed the 32-bit driver and perl. It worked immediately without tweaking gds32.dll or anything else. Thanks, - Tim ---In [email protected], <mark@...> wrote: On 10-11-2013 09:49, Helen Borrie wrote: > At 08:50 p.m. 10/11/2013, Mark Rotteveel wrote: >> On 10-11-2013 03:10, Helen Borrie wrote: >>> Some of the client tools that ship with Fb use fbclient.dll and just find >>> it right there. Other tools and drivers, you have to tell them how to find >>> it. Either use the PATH environment variable and put it right at the >>> beginning; or put a copy of the bitness-correct fbclient.dll in the >>> appropriate system folder. >>> >>> (On a 64-bit Windows, the 64-bit dlls go into the Windows folder and >>> 32-bit dlls into \Windows\sysWOW64; nothing in \Windows\system32.) >> >> That is not true: on 64 bit windows, the 64 bit DLLs go into the >> System32 folder (afaik an archaic method to get libraries and the >> searchpath and I believe Microsoft discourages it), and not in the >> Windows folder. > > Interesting. On my 64-bit Windows box, system32 is empty and all the 64-bit > dlls are in c:\Windows. This was a standard install from a retail pack of > Win7 Pro. My system32 folder (Windows 8.1, but also for Windows 7 on my laptop) contains +/- 3900 files. on the contrary my Windows folder has only 36 files. I have installed both myself from a retail install. Maybe something is wrong with your install? See also: http://msdn.microsoft.com/en-us/library/windows/desktop/aa384187%28v=vs.85%29.aspx http://msdn.microsoft.com/en-us/library/windows/desktop/aa384187%28v=vs.85%29.aspx -- Mark Rotteveel
