Zeoslib Portal

Hallo,
I have a PC with two clients:
- fbclient21.dll for version 2.1 in windows\system
- fbclient.dll for version 2.5 in windows\system

Both clients connect to the 2.5 server version and I cannot change this
unless I update the application that uses fbclient21.dll.

With application that uses fbclient21.dll I have error that cannot format message because the firebird.msg is for 2.5 version and I cannot use a firebird21.msg

If I put firebird.msg in Windows\system I create a conflict for different
versions of clients (2.1 + 2.5).

There is a way to put firebird.msg for 2.1 version in a directory that
not conflict with the one for version 2.5?

Thanks.

Hello louis,

you could try to put the fbclient21.dll and the corresponding files into the application directory of the application that uses this client.
Best regards,

Jan Baumgarten

marsupilami wrote:you could try to put the fbclient21.dll and the corresponding files into the application directory of the application that uses this client.

Not works, because in the search path (Windows\system32 there is fbclient.dll for 2.5 version

But I have a solution: I add an EnvironmentVariable via code that points the dir that contains firebird.msg of 2.1 version: SetEnvironmentVariable('FIREBIRD_MSG', path);

Best regards.

Hello louis,

that seems odd to me because usually windows searches for libraries in the application folder, where the exe resides first. Did you rename fbclient21.dll to fbclient.dll in the application directory? Another possibility is that the programmer of that application might just have hard coded the path of fbclient.dll to be windows\system32\fbclient.dll?
Best regards,

Jan

marsupilami wrote:that seems odd to me because usually windows searches for libraries in the application folder, where the exe resides first. Did you rename fbclient21.dll to fbclient.dll in the application directory?

Even if I have a fbclient.dll in application folder, firebird.msg doesn't automatically found I must set environment Variable to works ok.

Another possibility is that the programmer of that application might just have hard coded the path of fbclient.dll to be windows\system32\fbclient.dll?

No, I am the programmer, and path is not hard coded.

Louis