Update conflict resolution strategy

Thread View: borland.public.cppbuilder.database.ado

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Tony Mon, 12 Feb 2001 18:49

#5783

Author: Tony
Date: Mon, 12 Feb 2001 18:49

7 lines
1378 bytes

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.

Re: Update conflict resolution strategy

#5786

Author: Eric
Date: Mon, 12 Feb 2001 23:07

20 lines
1638 bytes

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

Re: Update conflict resolution strategy

#5790

Author: Tony
Date: Tue, 13 Feb 2001 04:17

29 lines
2052 bytes

Thanks for your response. I guest what I'm looking for here are specific
code examples of simple common stategies.

Eric <erico@mediserve.com> wrote in message
news:3a886bb7.4266382393@forums.inprise.com...
> 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
>

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads