| Subject | Re: [ib-support] Controlling updates to the same record by 2 users |
|---|---|
| Author | Dimitry Sibiryakov |
| Post date | 2002-08-02T12:32:46Z |
On 2 Aug 2002 at 11:47, Stevio wrote:
test the record for changes before sending UPDATE. If record has been
changed you may do anything you want: warn user, mix changes, reject
them and so on.
The way to do it depends on BD access components. For BDE, for
example, UpdateMode = upWhereAll is enough to reject second user's
work. I guess you are a programmer, aren't you? Everything is on your
fingertips.
SY, Dimitry Sibiryakov.
>What I would like to happen is that the changes by the second user areIf the second user uses "read commited" transaction, then you can
>rejected, or at the very least they are given a warning to say that
>this record has been updated since they opened it and do they want to
>go ahead with their changes.
>
>How do I do this? Can this be controlled through transactions?
test the record for changes before sending UPDATE. If record has been
changed you may do anything you want: warn user, mix changes, reject
them and so on.
The way to do it depends on BD access components. For BDE, for
example, UpdateMode = upWhereAll is enough to reject second user's
work. I guess you are a programmer, aren't you? Everything is on your
fingertips.
SY, Dimitry Sibiryakov.