At 11:23 AM 5/10/2004 +0000, you wrote:

>Hi
>
>If my delphi/IBO application is intended to be installed on various
>client machines, are there advantages/disadvantages in my
>application using either fbclient.dll or gds32.dll?

You should be using fbclient.dll, copied as gds32.dll.

>I am currently using firebird-1.5.0.4306-win32 /silent as part of my
>setup. As I understand things this option does not overwrite
>gds32.dll if it exists. Could this cause me problems if a client has
>a different version of gds32.dll installed, or are they all the same?

Yes, it could cause problems and no, they are not all the same.

>As i understand it i can replace/ update the gds32.dll by adding
>instcleint i[gds32]to my setup. But I am worried that
>updating/replacing gds32.dll may cause problems with my clients
>machines either now or in the future.

In fact, you don't need to run instclient.exe for IBO. Just renaming it
and placing it in the system directory is sufficient. It is mainly for
IBX, which decides the client is illegal if it doesn't have the build
details for InterBase.

>To me it seems more sensible to convert my IBO units to use
>fbclient.dll (I understand I can do this by: In ib_constants, change
>the first variable defined in that unit, viz. IB_GDS32:
>string= 'gds32.dll'; to IB_GDS32: string = 'fbclient.dll';). but are
>there any disadvantages in doing this?

There are various techniques, if you want to go this way - off-topic in
this list.

>It seems strange that IBO is
>not setup to use fbclient as firebird doc says gds32.dll will not
>always be supported.

Not strange at all. IBO is used with Interbase as well as with
Firebird. The correct Firebird client renamed to gds32.dll can be used
with firebird. The interbase client gds32.dll renamed to fbclient.dll
won't work with InterBase...

./hb