--- In firebird-support@yahoogroups.com, Paul Reeves <paul@f...>
wrote:

> I also suspect that none this actually matters. I've tried using

the current

> system (libname.local for each library that is local) and

fbguard.exe.local

> and fbserver.exe.local. Both yield the same results. fbclient.dll

and

> msvcp60.dll are loaded from the local images and msvcrt.dll is

loaded from

> <sys> dir. So, as far as the server is concerned, we looks like we

don't

> need to bother.

I also think you don't need to bother for anything like msvcp60.dll.
The .local files only have an effect if the executable tries to force
a path for a dll.

> But this does throw up another question - perhaps a client

application that

> really cares about the firebird client library used should be

installing

> the library in the same directory as the application and creating a
> myapp.exe.local file.
>
> I think this topic needs a little more investigation.

I think you could safely drop them all from the installation.

Sometime maybe we could write something more comprehensible than the
MS documentation to help users achieve what they want. Frankly,
anyone that is capable of installing multiple versions of a server on
one machine will be able make a few .local files manually.

Regards

Eric