>>>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?
>>
>>Have you check the Key Update in the view and the Where clause? There is some chances it can be the view the problem, not the table.
>
>We have several updatable fields. This is happening on the client side for each delete but I can't simulate it here. For me, it always work. Do you think the view may be corrupted?

I don't think the view is corrupted if it always worked. Can you reproduce the same error on your side? If not, it can be corrupted. But, what is the where clause? Key fields only, Key and modified Fields, Timestamps, ...? Does the key updatable fields represent "exactly" the key in your table.