MySQL ODBC ADO RecordSet Fehler: “Die zum Aktualisieren angegebene Zeile wurde nicht gefunden.”

irc.freenode.net / #mysql log:

[16:27] Hi. someone using mysql/odbc+adodb and having problems by post a record which has not changed? (i get always a error message (in the case there was no change) like: “record chould not found”)
[16:27] by post?
[16:30] jbalint, yes, example: Call oADORS.Update(Array(“Matchcode”), oADORS.Fields(“Matchcode”).Value) -> error
[16:30] jbalint, ive only a german error message so this maybe not useful
[16:30] ralf__: ok, what is it
[16:30] jbalint, the error message?
[16:30] yes
[16:31] jbalint, “DB.Err: #-2147217864 Native: #32 SQLState: , Die zum Aktualisieren angegebene Zeile wurde nicht gefunden. Einige Werte wurden seit dem letzten Lesen ggf. geändert.”
16:33] ralf__: does the way that “works” actually update the record?
[16:33] jbalint, yes
[16:33] ralf__: ok, lemme check something
[16:34] jbalint, you want to know the mysql-versions iam using?
[16:34] ralf__: nah
[16:34] ralf__: are you using ASP?
[16:35] jbalint, no, VB6 + “microsoft activex data objects 2.8 library”
[16:35] (i think thats mdac 2.8)
[16:35] ralf__: ok, are you using a connect string, or you created a DSN and saved it?
[16:36] yeah, it’s part of mdac 2.8
[16:36] jbalint, ive setup a odbc connection in windows odbc manager and use this
[16:37] jbalint, you want to see the “oADORS.ActiveConnection.connectionstring”?
[16:37] ralf__: in the advanced tab of the setup, did you check the first option?
[16:37] wait
[16:37] jbalint, no – i will try
[16:37] ok
[16:38] jbalint, (segfault from odbc manager) -> but its saved
[16:38] which version of the driver are you using?
[16:39] jbalint, driver (dll) = 3.51.14.00
[16:40] well i think the problem is when you update with the same value, it says “0 rows updated” and ADO thinks that the row could not be found
[16:40] by checking the “Return matching rows” option, it should report 1 row updated if it was found, but not updated
[16:40] you can try updating to a newer release of the driver

Genau diese Option “Return matching rows” in den Eigenschaften der ODBC Verbindung war es.

Ein aktualisieren des Treibers hat, auf den ersten Blick, nichts gebracht. Aber neue Versionen sind ja meist nicht schädlich.