Recent content by Chriss Miller

No tweak, I'm running Win10. Also, I showed you screenshots of my setup and talked about it, didn't I? Can you please just read what I wrote? And before you go Win10. I wonder why your error indirectly states the connection is already done. Try this and see whether it works when you don't try...

On top of the LASTKEY() solution you need to have a few standards. That is SET ESCAPE OFF and set the Cancel property of the Cancel button to .T., so a) ESC triggers it and b) clicking it triggers ESC. The Hacker's Guide tells oyu about the Cancel property on the same page.

One more thing to consider: MariaDB Server runs the MariaDB service that is mysqld.exe under the user MariaDB - more precisely NT SERVICE\MariaDB. The data folder in the installation has MariaDB with full contol in Security. If your data folder is elsewhere or even on yet another networked...

for you. Maybe it's Win11.

One more simple thing I tried for your information: I can change port in the ini and it works - of course after restarting the MariaDB Service. I just remember FTP uses random ports in active or passive mode for the data transfer after establishing the connection on some standard port and you...

Well, when you do that via the installation, it's totally plausible that does something. But just chaing a text file, doesn't make Windows change any firewall filters. MS knows the standard ports for MSSQL and MySQL and some more and has them open for local access, but also not necessarily for...

Did you change server to 127.0.0.1 when trying that from there? Even if, you're still using a network connection through a port and firewall rule are applied. So try changing the port back to 3306 in the INI and restart MariaDB and try with a connection string using...

If you changed the port in the INI after setup, I doubt this will establish any rules in the Windows Firewall. Did you use the MySQL driver before, with a MySQL Server backend and for got you configured exceptions for it in the firewall? I think it's a problem in that direction and may be solved...

I just deinstalled MariaDB Server to go through the setup once more. At this point there's an option to allow root user to access the db from remote machine, which is the case in your setup. You establish an appuser, though, so might not affect you. You have to do some configuration work in...

A successful connection is made fast, a connection fails only after a number of tries and at a timeout, that always takes longer. I don't know what happens, your AERROR tells the error origin is from within MariaDB, so some part of the connection has to work, otherwise the origin wouldn't be...

One more idea: SERVER=192.168.0.25 Since you're not using localhost and you're not using standard port 3306, a firewall could be your problem.

If I look back and interpolate all you said previously, I guess you will be able to connect and get correct results with the original MySQL Server you had and the 8.0.0.35 driver, IIRC. Anyway, you wasted your time in investigating the connection string problem, you have actual query errors, as...

access violation would mean you've got the password wrong, or the user name. Has nothing to do with the driver not working. A Syntax error would not apply to a connection string, a syntax problem in the connection string would lead to aynthing from driver not found to server not found and...

The least thing you could then do is lcString = oConnectMgr.GetConnString() gnConnection = oConnectionMgr.SQLSTRINGCONNECT( lcString ) IF gnConnection<1 AERROR(laError) SUSPEND ENDIF And if the code suspends look into the debugger watch window into lcString and into the laError array.

The work for me, though. Double checked and confiremed. The driver name has to just be exactly as stated in the Administrator. Notice wheil ANSI is in all caps, Unicode is not, to point out a difference. And without the exact driver name I get the error, as I already said. Look, if things work...