Microsoft is conducting an online survey to understand your opinion of the Msdn Web site.If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site. Description: When I try to update a record but there are no changes in the record the update fails with the following error text: "Row cannot be located for updating. Update() End With If the information in the database is the same as what's in the update then the error occurs. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". Left on it's own, *Access* forms rather insane update queries depending on *all* fields values, timestamps and who knows what.Some values may have been changed since it was last read." As far as I can see there are two work-arounds: 1. First check if there are changes in the record How to repeat: rs. Conn, Cursor Type Open Keyset, Lock Type Lock Pessimistic) With rs . Same problem here, My SQL ODBC Driver 5.1 Access 2007, vba code .update doesn't work when the value is already in the table. Please try to tell Access how to form UPDATE queries as described above: rs Customers. Value = ad Criteria Key and catch any error it might throw.Always Run-time error '3197' The Microsoft Office Access database engine stopped the process because you and another user are attempting to change the same data at the same time. .update works fine when it runs for the first time. If you omit this, you'll just end up with updates really failing cause Access tried to exact-match floats, blob's and so on.As of second time -Rob, Klaus, as stated in original report (Bug#7160), I will really need ODBC trace from Driver Manager to see what's actually happening. As for error being thrown, it is rather straight forward... The update to change the dates croaked with the "row cannot be located for updating" error.
If it was, My SQL server would return "found_rows" (1+) instead of "affected_rows" (0).Just a heads up that I'm working with SLX support on this issue now. :) We were hit with the issue again this week, and this time it was on brand new records. The record is found, pulled client side, the field values are set, then it fails on the .update statement.you said you want to update row but updated_row_count returned was 0 (as there was nothing to update).This occurs since first option in DSN config ("Return Matching Rows") is not checked even we say clearly it should be in manual.Microsoft is conducting an online survey to understand your opinion of the Technet Web site.
If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.