Some values may have been changed since it was last read.*Native Error: 32 *SQL State : Thanks, Bill N Bill, Another process could have changed a value that the DB manager is using to locate the row. Value := ad Criteria Key; ad Criteria Key is defined in ADOInt. If your table don't have a primary key make sure u fill every single field with a value instead of NULL (I'm not sure whether this is a correct approach, but at least it work for me). I' using Delphi 7 with ADO components with an Access database. Is there a way to set the SQL generation to just use the key? I delete one record and when I reopen my app I find that two have been deleted instead. "Brian Bushay Team B" When you use clientside cursors and make changes or delete a record in the client ADO needs to Generate SQL to update (or delete) the Record in your database.I know this is possible, but cannot find out how this is done from D7. I have a form that has a couple of grids and databound controls.Without this, ADO will default to taking *all* fields as the key and stuff these in the SQL WHERE clause it constructs on the fly. The datasources are set to some TADOQuery's which have master datasources too.However, my table has a primary key defined and rows can be uniquely identified using this key (an Int). Recently added an insert/update trigger to a table in SQL Server to populate some fields from a 2nd table.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). Since then inserting a new row gives the error "Row cannot be located for updating".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.I have searched this NG and also Tamarack but cannot find this message anymore. It is a simple table I am trying to update, not a join.
What causes this error and how can I handle it in my exception handling.I really don't understand how coming out from this nightmare. IDMaster, the linking field in Detail Table, is also a Long Integer.If I set it to Integer, I cannot set the relationship in Access.This process of extracting the elements of a collection is called refers to a LOB object attribute, then you must first initialize it with a value of empty or null. Also, if you are updating a LOB value using some method other than a direct to set the column to the value previously specified as the default value for the column.If no default value for the corresponding column has been specified, then the database sets the column to null.