The issue I have with this is that B may not even edit the record. Regarless of whether they intend to edit it or open the record and walk away from their screen, A is not allowed to save any of their changes.
Michael,
The way Optimistic Locking typically works is that you don't set timestamp when a record is loaded (retrieved) but when saved. This prevents that "can't edit" scenario you mention.
When a user loads a record you get the lastSaveTimeStamp. You store this in a hidden field, session etc. When they save the record you check that value see if the lastSaveTimeStamp has been changed by another user and react appropriately.
Personally, if there is any contention I just let the user know that they need to examine the updated data and change it accordingly.
-- Brad Perkins _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
