Le 21 févr. 06 à 15:26, Rony Cesana a écrit :

> Given that the Win32 specific readme says that "It is inteded that
> future
> versions of Firebird will not attempt to install gds32.dll into the
> <system>
> directory and ultimately it will be completely removed from the
> distribution", I wonder whether the time to use instclient.exe has
> already
> come...

As far as I remember the current installer actually use
instclient.exe for the purpose of installing the client library
(wether named fbclient.dll or gds32.dll) to the system directory.

I must admit I didn't use the installer for sooo long (though it is
excellent).
We distribute FB with our apps by copying it (well the minimal
required sub-structure of its directory tree) to some target
directory tree then we use instsvc to configure the services.

The installer is very useful when you want to setup a single generic
standard server instance to one machine, one that will potentially be
used by multiple applications from different providers.

We proceed differently. The FB we distribute within our own
application directory tree uses a nearly default (but slightly
modified) firebird.conf to disable the local protocol and to use a
port different than the standard one. Our own setup then creates the
service definitions such that they do not conflict with one standard
configuration and our application know on what specific port to call.
This way, we have our own isolated firebird server, even though the
end-user happen to have another one installed on the machine.

So you see, there are a number of options.

--
Olivier Mascia