HomeFlySpeed SQL QueryNone of the dynamic libraries can be found: libmysql50.dll, libmysql.dll

None of the dynamic libraries can be found: libmysql50.dll, libmysql.dll


I get this error message when trying to create a connection to MYSQL under Windows. My installation doesn't have a DLL library named as above - rather it is named "mysql.dll". What to do?
Joel | email
December 12 2007, 01:30 PM
Dear Joel,

These libraries could be taken from the MySQL Server distributive and placed in the program installation directory. The next minor version that will be released till the end of this year, will be able to work with MySQL without these libraries. Sorry for the inconvenience this may cause you.

Sincerely
Sergey Smagin
Sergey Smagin | email
16 hours, 56 mins since original post
I'll definitely try your next release, but my concern is that aside from where they're located, I don't seem to have the DLL's mentioned in the error message at all - rather my DLL library is called "mysql.dll". Is there more than one version of MYSQL, with different DLL library names?

Also note that I didn't install MYSQL in the normal way - it came (a stripped down version possibly) with Slimserver (http://www.slimdevices.com/su_downloads.html).
Joel | email
1 day, 3 hours since original post
Dear Joel,

These DLL can only be obtained from full windows distributive of MySQL server.

Sincerely
Sergey Smagin
Sergey Smagin | email
1 day, 11 hours since original post
I got the libmysql.dll from the standard distribution and put it in the same folder as FlySpeed SQL Query. Now when I try to connect I just get the error "SQL Error: Can't connect to SQL server on "localhost" (10061). I know I have the port, userid and password correct, because I have another application that can successfully connect to this database using them (it's not running when I'm working with FlySpeed though). Only difference is FlySpeed is on the same machine as MySQL, the other app is on another machine on the network. I tried replacing "localhost" with 127.0.0.1 and with the IP of the machine, but it didn't help. Any ideas?
Joel | email
3 days, 9 hours since original post
This topic is closed