At 10:39 AM 27/02/2007, you wrote:

>Yes, that does work. And throwing a copy of fbclient.dll into the
>folder where I usually store IB_SQL did the trick as well.
>
>I suppose I expected IB_SQL to know where to find the DLL, but it's
>really not that big a deal. Thanks for the response.

IB_SQL is an application. It "knows" where to go to find the client
because the application has code that tells it where to look. The
system directory is the place of last resort if the application code
has been compiled without an explicit path to the client library.

There are several ways you can deal with this. You can recompile
IB_SQL, of course, and give the compiler a way to know the *name* of
the file it is looking for - search the release notes for "GetFBClientLibName".

The main thing is for the application to find the client library. If
it can't find it in the same directory as the executable then it will
use the system path. So the important thing is to make sure that the
location where you want it to find the client library that you want
it to find it, is to add that location to the system path *ahead* of
system32 and any other paths defined that will find a client lib of
the same name.

Helen