Subject Re: [IBO] gds32.dll stack problems
Author Helen Borrie
At 07:35 AM 10/08/2004 +0000, you wrote:
>I am having problems with an application which is stable on my system
>but has stack problems on my customers machine.
>I notice using madexcept that the machine has an interbase 6 gds32.dll
>I ahave asked my customer to upgrade the dll the the firebird
>1.5.xxxxx version but would I expect to get stack exception errors
>from this ?
>I was under the impression that from Firebird 1.5 gds32.dll was no
>longer used and that fbclient.dll was now used ?
>Is it the case that fbclient.dll now needs to be in the windows/system
>directory and all gds32.dll's should be deleted ?

If the client is connecting to a database on a Firebird 1.5 server, it
needs a Firebird 1.5 client. If you have the IB 6 gds32.dll being used as
the client, of course you are going to have stack exceptions. You can't
get orange juice from an apple!!

The Fb 1.5 client is officially called fbclient.dll and it lives by default
in the bin directory of the server installation. Unless you modify IBO, it
expects a client named gds32.dll located either in the application
directory (i.e. where your exe is) or in the system path.

So, if you don't want to change IBO, then change the library. For IBX, you
have to run a program (also in the bin dir) named instclient.exe. For IBO,
all you need to do is copy fbclient.dll to the client machine (application
or system 32) and rename it as gds32.dll. Of course, if the IB6 (or any
other) version of gds32.dll is there, you'll have to move, delete or rename
it first. If you find you can't do that, it means that the library is
already loaded, so you'll have to reboot the machine first.