>If I allways DELETE, then INSERT whenever someing is edited, this will make a huge amount of DELETED records. It will also be slower as this is 2 commands instead of one.
>
>I cannot understand why VFP does not allow us to do a TABLEUPDATE so that the last user ALLWAYS wins. Maybe I am missing something.

The last user does always win. But the nature of SQL views (and SQL itself) uses a key or set of keys to find a record to update with its UPDATE statement. If there are no records that match the key (they are deleted), no records are updated.

I'm curious, what sort of business situation has one person deleting an entity, and another modifying it?