Row can not be located for updating

Hello, I have a legacy application written in VB6 and using Oracle OLEDB Provider (version 9 and updated to the last ones from oracle site) I've a problem during insert of a record using recordset method (Add New).

The returned message is "Row cannot be located for updating.

The insert/update trigger pulls information from other tables and populates some fields of the table being inserted/updated which makes for ADO to not being able to find the just inserted record back.

" I know that problem is caused by a Before Insert trigger that I CANNOT change. I tried to use the recordset Property option "Update Criteria" = ad Criteria Key without success !

He has to scan the whole db to find all possible candidates and if he finds too many, or none, he cant update anything. The default for ADO generating SQL is to use all the fields and values you originally queried from the database to find the in your 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" Yes, I have a single column meaningless integer key for each table. I was about to resort to submitting the SQL myself, using the statement that you showed below.

If you have triggers that update your records or with some databases Date Time fields where miliseconds get truncated the values of your clientdataset may not match the records in your database after an initial edit. COM Do you have primary key in every table affected by delete? Net The fastest way to access MS SQL Server, MS Jet (Access) and Interbase (through OLEDB) "Carl" In this instance, I am just building a desktop application. Is there a way to set the ADO components so that they just use the key to find the record? Vassiliev" Do you have primary key in every table affected by delete? Net The fastest way to access MS SQL Server, MS Jet (Access) and Interbase (through OLEDB) "Carl" Do you have primary key in every table affected by delete? Net The fastest way to access MS SQL Server, MS Jet (Access) and Interbase (through OLEDB) "Carl" I can see that this is a problem for many people. I have just installed Jet 4.0 SP 8, without solving my problem both with Windows 98 and Windows 2000. Relationship is between field ID (autoincrement field and primary key in Master Table) and IDMaster (numeric field in Detail Table). Cursor Location is cl Use Client and Cursor Type is ct Static Anytime I add a new record in Detail Table I can see that IDMaster is filled with the proper value from Master Table: When I post the record its primary key is 0. If I refresh, I get the error message "Key value for this row was changed or deleted at the data store.

Deleting some rows may occur if there is no primary key, because ADO execute query: DELETE FROM [Some Table] WHERE .... Deleting some rows may occur if there is no primary key, because ADO execute query: DELETE FROM [Some Table] WHERE .... Deleting some rows may occur if there is no primary key, because ADO execute query: DELETE FROM [Some Table] WHERE .... Detail Table has an autoincrement field as primary key. The local row is now deleted" and actually the row seems to disappear.

If there is no primary key, WHERE may select some rows. If there is no primary key, WHERE may select some rows. If there is no primary key, WHERE may select some rows. But If a close the de and re-launch it the row is there, with the proper ID value! If I delete or change the record I get the message "Row cannot be located for updating.

Search for row can not be located for updating:

row can not be located for updating-28row can not be located for updating-78

I am getting an EDatabase error that says 'Row cannot be located for updating'.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “row can not be located for updating”