| Subject | Re: [firebird-support] Unable to get Firebird ODBC driver working in 64-bit |
|---|---|
| Author | Helen Borrie |
| Post date | 2013-11-09T21:45:31Z |
At 09:12 a.m. 10/11/2013, bandersnoot@... wrote:
It seems you need to go and do a bit of digging, possibly even contact the vendor of the embedded app to get some of the answers.
On the Good News side, the "embedded thing" in an embedded installation is not the database, but the method of accessing it. You can set up an embedded structure of your own, or use a Classic server instance, and access that database independently of the vendor app....during user downtime, natch.
Helen Borrie, Support Consultant, IBPhoenix (Pacific)
Author of "The Firebird Book" and "The Firebird Book Second Edition"
http://www.firebird-books.net
__________________________________________________________________
>I am trying to develop a simple reporting script in perl. I've done this many times using the ODBC driver for SQL Server with good results.What you are describing here sounds like a full server install, not an embedded one. Firebird embedded comprises both client and server. That is the client you should be trying to connect to, The fbclient.dll (alias gds32.dll) client libraries are not in this picture.
>
>One of our vendors uses a captive or embedded Firebird database, and I am trying to get an ODBC driver working on the server so I can run my script.
>
> From the best I can tell, the Firebird client is 32-bit, though I'm not sure. I found a fbclient.dll in C:\Program Files (x86)\Firebird\Firebird_2_1\bin\ and copied it to WINDOWS\system32\ and renamed it to gds32.dll.
>The server (where I'm trying to get the script running) is Windows Server 2008 R2 SP1 64-bit. Because it's a server and supported by the vendor, I can't mess with the Firebir d DB installation.Find out whether the embedded server dll (fbembed.dll) has been renamed to fbclient.dll. This is usual. The size of fbclient.dll will be much larger than the ~400 KB size of the lone client.
>I am in ODBC driver hell.I don't think so. I think you are in Firebird client hell. Embedded installations are always custom, with fbembed.dll (usually renamed) required to be in the same directory as the application executable. What's more, if one application has an active embedded connection to the database you are targeting, then no other application (or script) can access it.
It seems you need to go and do a bit of digging, possibly even contact the vendor of the embedded app to get some of the answers.
On the Good News side, the "embedded thing" in an embedded installation is not the database, but the method of accessing it. You can set up an embedded structure of your own, or use a Classic server instance, and access that database independently of the vendor app....during user downtime, natch.
Helen Borrie, Support Consultant, IBPhoenix (Pacific)
Author of "The Firebird Book" and "The Firebird Book Second Edition"
http://www.firebird-books.net
__________________________________________________________________