A typical way to picture data like this is as a table with rows and columns.In database terms, each row is often referred to as a record. My problem is, this Requery process is painfully slow.Can anyone please tell me why that Resync method works and why everything else fails even if I perform a Commit Trans ? The second thing I can think of is that you do not have a unique identifier for the row, so when you update a row which is similar to another, this error is shown to stop a possible update to the wrong row.Good stuff Could you mark the thread as resolved please?(on the Thread Tools menu above) My guess is that the standard behaviour of Find invalidates the recordset, as it filters it (and as such effectively creates a new recordset).
https://web.archive.org/web/20130417....com/kb/300586 The workaround is to run the update as a separate ADO command, and then refresh the ADODC.
To get around delay issues with updating the database and the error: "Row cannot be located for updating.
Some values may have been changed since it was last read.", I use the following code to force the database to be updated.
Each column (sometimes referred to as fields) contains a value for each type of data: first name, last name, and so on.
, and you use it to identify each row in the table.