In the FB1.5 client install, the option to include a copy of the
fbclient dll as gds32.dll is "Generate client library for legacy apps?
I should have referred to the "legacy app gds32.dll". Sorry for the
misspeak and thank you for explaining the path issue.

--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:

> At 11:16 AM 8/05/2004 +0000, you wrote:
>
> >Is it OK to have both these dlls in system32? My app uses the

legacy

> >gds32.dll but the FB utils like gbak will use fbclient.dll. I'm
> >getting an error on gbak that says another process has the database
> >open. I have tried several very simple versions of the gbak .bat

job

> >on the same PC where FB is running (and the app using localhost).
> >Thanks.
>
> What are you talking about "the legacy gds32.dll"? Legacy from

what?

>
> If you need to use a client named "gds32.dll" then you have to have

it

> built by the program instclient.exe (located in the \bin

directory). It's

> not a "legacy gds32.dll" but the current fbclient.dll with a

different name

> and an internal version string that Borland's products, e.g. IBX,

will

> recognise.
>
> Having both in system32 shouldn't matter. Basically, if your

programs

> expect to load a library called gds32.dll from the system path then

they

> will try to do that. Moving fbclient.dll to system32 won't change

that.

>
> /heLen