At 10:34 a.m. 4/12/2012, Robert Martin wrote:

>Hi
>
>Maybe not an appropriate IBO question but here goes...
>
>We are looking to upgrade our users from FB 2.0 to FB 2.5.2. Previously
>we have relied on the FBClient.dll being in the system directory.Â
>However I read that this is not the best option.
>
>Helens FB install guide says....
>/
>//'Furthermore, as we want to allow multiple engines to run
>simultaneously we would be creating our own DLL hell if we continued to
>encourage the practice of using the system directory for the client
>library. /
>
>/So, from Firebird 1.5 on, the client library for local use on the
>server has resided in the \bin directory along with all the other
>binaries. For those whose local server applications still need to find
>the client library in the system directory, the installer provides the
>option (unchecked) to copy the client to the system directory and also
>to rename it to ///gds32.dll///, if need be.'/
>
>
>I cant see how IBO would know which \bin directory to use to access the
>FBClient. So should we be installing FBClient.dll to our applications
>installed directory or is there something I am missing?
>
>We have a heap of FB client PCs that need to be upgraded, is it ok for
>our software to just copy the FBClient.dll in or do we need to do other
>files (.msg file?).

As Jason said, plus, if you are using any of the service components or the g* utilities from the client side, you need firebird.msg. You would also be well advised to have the correct Microsoft c and c++ runtimes (msvcp71.dll and msvcr71.dll for the v.2.5 client and engine) in the application directory as well, in case they're not in an accessible path. Use the ones that are in the official installer.

Helen