>>>Erik,
>>>
>>>This is interesting. If I change the update criteria to Update using SQL Delete and Insert. Then I change some records and issue the tableupdate then requery I get the old record and the changed record?!?
>>>
>>>So it seems like the SQL Udate is not working correctly.
>>>
>>>Any more thoughts?
>>
>>If you have SET DELETED OFF that would make sense... since the requery() brings you the active and deleted record. Remember, DELETE in xBase files only changes the deleted status.
>>
>>BOb
>
>I think he will get this even with SET DELETE ON. The fact tat this happens only with DELETE THEN INSERT, says that the DELETE part of the update isn't working (just like the update wasn't working before). This tells me again, that somehow the records in the view are lacking sufficient PK information to relate to a record in the base table, so the DELETE FOR statement finds no records (but the INSERT doesn't need to find base records, so it succeeds).
>
>I think the solution to this problem will come from disecting carefully the contents of the view before the update is run.

Erik,

I have not completely solved this problem yet but I believe you are correct. I looked at the data on the Oracle side and found that the record that I added the key field had a length of 50 but the record I was trying to delete had a key field lengh of 7.

This is strange that I would have to trim the key field before trying to go back to the Oracle table but that seems to be the case.

Thanks for your suggestions and comments.