I had a *NIGHTMARISH* time with update conflicts until recently, it turns
out that it involved using the update criteria 'Key and Modified Fields' in the 'SQL Where clause includes' area. When a memo field was updated, it caused the 'Update Conflict' to occur.

Change it to 'Key Fields Only', and specify the key fields directly by placing the 'key' symbol next to the field; no more update conflicts since then. :)

If you build the query programmatically, then use the following:

=CURSORSETPROP('WhereType', 1)
=CURSORSETPROP('KeyFieldList', cKeyFieldList)


>I know to look towards keys, etc when there is an Update Conflict error, but is there anything more descriptive that points to what is actually causing the conflict to narrow down the search? If it knows enough to return the error, it must know what the cause was. What a great help if it would pass that along to the developer. Is there a way already? Thanks!
>
>Regards, Renoir