>>>One of my clients is having an update conflict message when deleting a record. That record is from a view. We do not use a DBC so there is no trigger. The only thing I can see is that there was a duplicate key in the table. However, we checked that and there isn't. We checked that with SET DELETE OFF and no pack was done on the table since its creation. Can someone tell me what else can cause an update conflict at delete time on a view if this is not a duplicate key?
>>
>>Michel, I have seen this error using remote views and MS SQL Server when I do TABLEUDPATE in the view and then attempt another TABLEUPDATE without =REQUERY() in between. I will get this error on the second TABLEUPDATE whether I am changing data or deleting. I don't know if the behavior is the same with local tables.
>
>I don't do TABLEUPDATE() because the client didn't want to have a buffering. The changes are saved immediately.

Just a long shot.......
In an app I inherited, which doesn't use buffering either, the clerk gets an occasional update conflict message because she/he bangs to "Save" key too hard and causes a key bounce. Trapping the key strokes immediately before the save code is executed seems to have cured the problem.

Jerry