However, my table has a primary key defined and rows can be uniquely identified using this key (an Int).
I've read some time ago in this NG (I believe) that you can limit the ADO where statement construct by informing the ADO recordset about this primary key (or rather: dropping the other fields). Presumably the trigger's you've added are connected to the table you Hi Brian, thanks for taking the time to answer.
Some values may have been changed since it was last read. Sometimes editing my data in a grid, I get an error described above: "Row cannot be located for updating.
I added the flag "Option=2" to the end of my ado connection and this fixed the issue.
Properties['Update Criteria'].value := ad Criteria Key; m IKE "Ahmadi" ADOTable have not the Before UPdate and Before Delete events. I have found that I get spurious errors with ADO with MDB or SQL-Server databases when focus is on a data-grid when I insert into that same table.
Now, I just move focus to some other component, typically a tabbed notebook or groupbox component in which the grid resides, in the Before Insert of the TData Set.
Recently added an insert/update trigger to a table in SQL Server to populate some fields from a 2nd table.
Since then inserting a new row gives the error "Row cannot be located for updating".