At 07:30 p.m. 21/07/2014, Venus Software Operations venussoftop@... [firebird-suppo wrote:

>Yes, I already have a copy of the 32 bit fbclient.dll in my application folder. Why would the FB ODBC driver expect such an old name of dll? I can of course rename the fbclient.dll to gds32.dll, but where do I put it so that the ODBC is happy. I would love to use FB 64 if possible.

Look at the Subject of your thread! Where did that message come from, if your application and driver already know the real name of fbclient.dll? You need to look at your application code and your ODBC driver setup and find that mismatch.

Put the client where the ODBC driver can find it - try SYSWOW64, since that is where 32-bit apps and libs expect it to be. (You still have not confirmed that you want to run this 32-bit app on the same box as the 64-bit Firebird...)

Helen Borrie, Support Consultant, IBPhoenix (Pacific)
Author of "The Firebird Book" and "The Firebird Book Second Edition"
http://www.firebird-books.net

That came up when I tried to verify a 32 bit app connection string to 64 bit FireBird via 32 bit FB ODBC driver.  The app has no knowledge of fbclient.dll or gds32.dll directly so I assumed FB ODBC to looking for gds32.dll.

connstring: Driver={Firebird/InterBase(r) driver};Dbname=C:\MayPathname\mydata.fdb;PWD=masterkey;UID=SYSDBA;

Does such an above connstring limit me to 32 bit FB?

Interestingly I have another app (ReportManager from sourceforge.net) that is 64 bit and it expects FB DSNs (it can do connstrings but DSNs created via the 32 bit app eases support work)

So I have two ways to get to the data, the connstring way is 32 bit and the DSN way is 64 bit

Yes I wanted to run a 32 bit app (limiting FB ODBC to 32 bit) on a 64 bit OS with 64 bit FB if possible.

Please advise

Kind regards
Bhavbhuti