🚀 go-pugleaf

A  very simple strategy we use is to have a column in the table that
stores last modification date/time and by whom.  When a client
attempts to save the record  this column is compared against a value
stored when the user opened the record.  It is simple but suit our
needs.

On Mon, 12 Feb 2001 13:49:02 -0500, "Tony" <hse@hill-soft.com> wrote:

>Does anyone have or know of a cppbuilder or delphi example of resolving
>update conflicts using client side static cursors, optimistic locking and
>Access 2000? My app has many bound controls so the code to resolve conflicts
>need to be in events such as AppsRecordChangeComplete. I'm looking for
>something very simple (as a starting point) that would tell the current user
>that another user had modified the underlying data and ask the user if they
>want to abandon their changes or overwrite the other users changes.
>
>


Eric