>>>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 am confused, how do you get a view without a dbc? Is it possible that two forms in the same machine are accessing the same cursor?
>
>I'm sorry, yes, we use a DBC but the view is composed from free tables.
>
>The test we did this morning was with only one instance with one form and we got the error.
Michel,

Does this occur when you delete the record in the view or when the tableupdate is executed to write the deletion back to the table?