Cannot load dll fbclient.dll

calou · Post by **calou** » Thu 11 Mar 2010 10:32

Hello,

I have installed a client software on a new computer.
For connect to the database i do this :

  
IBCConnection1.ClientLibrary:='fbclient.dll';
  if FileExists('fbclient.dll') then
    showmessage('OK');
  IBCConnection1.Connect;

I have the error message cannot load fbclient.dll but the showmessage occurs (i use an IBCConnectionDialog to enter the parameters for the connection)!!
There is no firebird installed on the computer. I remark that if firebird is installed there is no problem.

Thanks for help

Regards

calou · Post by **calou** » Thu 11 Mar 2010 17:08

It seems that it is a virtual box problem!
On VmWare it works good.

I don't understand why

Regards

calou · Post by **calou** » Thu 11 Mar 2010 21:38

Does IBDAC need other files than fbclient.dll to connect to a database that i will not install on the virtualbox computer? (it is a windows XP)

Thanks for help

Regards

Archer66 · Post by **Archer66** » Fri 12 Mar 2010 11:40

Do you use embedded version of Firebird ? It needs other files too.

calou · Post by **calou** » Fri 12 Mar 2010 13:50

Hello,

I use firebird 2.1. Not embedded version

Regards

Falcon · Post by **Falcon** » Fri 12 Mar 2010 13:53

Applications based on IBDAC require InterBase/Firebird client software only. IBDAC dynamically loads InterBase client DLL (GDS32.DLL or FBClient.dll for Firebird) available on user systems. To locate DLL you can set either the global variable GDSDLL, defined in IBCCall unit, or TIBCConnection.ClientLibrary property with the path to the client library. By default IBDAC searches client DLL (GDS32.DLL) in directories specified in the PATH environment variable.

calou · Post by **calou** » Fri 12 Mar 2010 13:59

I don't need to locate the dll. I know where it is and i give the path to the ibcconnection.clientlibrary
Further more i know that the dll exists and the ibcconnection find it because the showmessage occurs and the application works on other computer.

Regards

Falcon · Post by **Falcon** » Mon 15 Mar 2010 08:03

Try to use

Code: Select all

LoadLibrary(Path);

WIN API to chech whether .dll is valid. Possible the problem is with it.