Win10, MariaDB 10.2.7

Thank you for your reports.
I guess generated queries are different, and that is probably because of different versions of ADO, which constructs the query in this case.
Could you please provide your CREATE TABLE? I guess that is (auto_increment, varchar, text, date, time), but still.
And you test script could also help, if it was possible to provide

Actually I used more or less the following script for my test:

https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-examples-programming-vb-ado.html

For MariaDB I have adjusted the connection string to the following values:

conn.ConnectionString = "DRIVER=

;" _
& "SERVER=MariaDBserver;" _
& " DATABASE=odbctest;" _
& "UID=xxxxxxxx;PWD=xxxxxxxxxx;PORT=9999;OPTION=17317930;"

And I switched to
CursorLocation = adUseClient

The create recordset statement was produced by the following code:

rs.AddNew
rs!Name = "Monty"
rs!txt = "Insert row"
rs!dt = Date
rs!tm = time
rs.Update
rs.Close

The create table statement is the following:

'create table
conn.Execute "DROP TABLE IF EXISTS myado"
conn.Execute "CREATE TABLE myado(id int not null primary key AUTO_INCREMENT, name varchar(20)," _
& "txt text, dt date, tm time, ts timestamp)"

Do you think this information is good enough for your analysis?

I usually test on W10, and I tried with adUseClient - could not re-create your problem. Apparently that is not Windows version what matters. I'd imagine that ADO library version is the best candidate.

Could you please try if the problem repeatable with MySQL connector? and if it is - does NO_CATALOG=1 in the connection string cures that. I saw in the log, that your application tries to connect using MySQL 5.2 connector, but driver manager cannot find or load it

This is very funny.

I had MySQL 5.2 connector installed a while ago, but uninstalled it half a year ago.

Now I have only the MariaDB 2.0 connector installed. Nevertheless the Win10 ODBC manager still shows a MySQL 5.2 connector under section driver.

2 questions:
a) Why does the ODBC manager try to load the MySQL connector, even I explicitly refer to the MariaDB connector?

b) How can I clean the leftover entries for the MySQL 5.2 connector in the ODBC manager?

I will try the "no-catalog" parameter after I managed to clean the odbc entries...

I don't know what your application does I just noticed that in the log, that prior to connect with mariadb connector, it tries mysql connector.
You can remove leftovers with regedit HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI and there you can find driver entries. For 32bit drivers you might need to go toHKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBCINST.INI
Besides individual driver entries, there is list of installed driver under in "ODBC Drivers" there.

DSN's in ODBC.INI, but also they can be under HKEY_CURRENT_USER

If NO_CATALOG helps with mysql connector(if it's vulnerable for the same problem), then probably implementing the same functionality will be the solution for your problem

I always use the same test program:
https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-examples-programming-vb-ado.html

Thanks to your instructions I could delete the obsolete entries in the odbc manager.

In a first step I have tested the same code as before with the same result. Therefore the mysql driver entries did not have any effect - same error.
Now I will install the mysql driver and test the NO_CATALOG option...

If you didn't do other modifications to the script,then it's hard to imagine why would it connect using different drivers.

And one more quick question - don't you get exception that "id does not have default value" with default table structure from that example script? because it's not auto_increment. Or you made modifications to it?

You are right - sorry that I did not mention it. I use the following statement:

'create table
conn.Execute "DROP TABLE IF EXISTS myado"
conn.Execute "CREATE TABLE myado(id int not null primary key AUTO_INCREMENT, name varchar(20)," _
& "txt text, dt date, tm time, ts timestamp)"

Still trying to get the mysql odbc driver to work. As soon as I have results, I will let you know.

I managed right now to run the same test with the mysql ODBC Driver (5.3.9) on the same Win10 machine. I did not put the no_catalog-option, but it worked without problems.

I will attach the sql trace and the adapted vb script.
SQL.LOG
ODBC_test.txt

Interesting. Ok, I will investigate more, compare logs, and will try to figure out what causes double dot. Thank you for your help!

Any progress on that issue? Other people experiencing this issue?

Sorry, there was no progress on my side on this issue. And no, other people did not report similar issue.
I will get back to it once I've done with my current tasks.

I have uploaded library with one thing fixed, which I think is best candidate to be the reason of your problem. Since I cannot repeat it, could you please check if it has any effect? and maybe, in best case, fixes the problem.
This is 3.0 connector. I can provide 2.0 library with the fix, if needed.

Did you have the chance to try? Latest releases(3.0.3 and 2.0.16) contain this change as well

Hi baumgaphil, have you had a chance to verify if the issue still occurs for you?

In two weeks, we will close this issue as incomplete since it will have spent a long time waiting for feedback.