Update Conflict Resolution [1585]

[Irwin]

I am looking for the proper way to handle en error 1585 on a data entry form that was designed to use optimistic buffering. Any help or thoughts would be appreciated.

Here is the scenario of my problem.
1- USER One is in view mode on an order.
2- USER Two then edits that order.
3- When USER One trys to change the order they are viewing or even close the form, an update conflict occurs.

My question is: What is the best way to stop this from happening completely or the best way to resolve the conflict without damaging data records?

Your Advice is Always Appericated.
Thank you in Advance,
Irwin

 

[mkrausnick]

I would make the viewer read-only, with an EDIT button. When clicked, the EDIT button would re-read / requery / refresh the data to get the most current field values. You can also reduce conflict errors be reducing the SQL WHERE CLAUSE section of UPDATE CRITERIA to just "KEY AND MODIFIED FIELDS", or even "KEY ONLY" if you like the sledgehammer approach, rather than "KEY AND UPDATEABLE FIELDS".

Mike Krausnick
Dublin, California