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?

>John, Jeff- there are a specific set of circumstances that cause a view to delete its recods- I wish I could remember clearly, but I can only remember vaguely, because I have dealt with this before- I think it is when you issue a TABLEUPDATE, and there are no values in for those that can be used in the WHERE clause. IE, the key fields are empty, or if UpdateType is set to changed fields, those fields are empty. Take this with a grain of salt...
>
>
>>Hi Jeff --
>>
>>The part of this whole exchange that blows me away is that a TABLEUPDATE deletes the record from your view. Besides that, the Update Conflict could be caused by a NULL or invalid value in a column (field). Look over your back-end table structure. Also, are there any sequences defined for any columns in the Oracle tables? If you try to update those fields, ka-blam.
>>
>>>Changed to just key fields. changed to table buffering. Now I can change the record with out it giving me an error. I issue the tableupdate() and it deletes the record from my view. Tableupdate() returns true. Requery() show the data before I changed it.
>>>
>>>Thanks for your help but I think that I am going to call it a day. I will work on this more tomorrow.