On Tuesday 02 of October 2012 12:08:42 Marc Weustink wrote: > Ludo Brands wrote: > >> Please I got a problem with libpq.dll library file, want I tried to > >> select the Connected property to True, I received the Error: Can not > >> load PostgreSQL client library "libpq.dll". Ckeck you installation. > >> > >> The library has been installed and copied to the project file. > > > > Libpq.dll has many dependencies. Probably one of them is not satisfied. > > Here is the list of files I needed to copy on a wine system to get > > libpq.dll loaded: > > comerr32.dll > > krb5_32.dll > > libintl-2.dll > > libpq.dll > > pg_dump.dll > > pg_restore.dll > > libeay32.dll > > ssleay32.dll > > Don't copy around dll files. This makes the mess worse. Make sure the > postgres bin folder is part of your user/system path. > > > A problem we encouter lately is that other software vendors come with an > outdated ssleay32.dll, which they put in sytem32 or int the path before > postgres. simply deleting the outdated ssleay32.dll will solve the issue > (as long as the postgres version is in the path)
Yes, such problem can exist when on client machine is installed an bank card reader which puts old ssleay32 into system32, but I had problem with Visual C++ runtimes (cannot load libpq.dll on some machines, on some works fine), so decided to use mingw compiled libpq (and then it uses only few dll's: libeay32.dll libpq.dll pg_dump.dll pg_restore.dll ssleay32.dll , now everything looks ok. Also, to prevent ssleay32.dll problem I'm putting needed dll's into client app folder. zeljko -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus