Hi Dimitry,

This testing of the record for updates is exactly what I need, but I'm using
Interbase Express components (I should have said that in the first email).
How can I test the record for changes before posting it?

Thanks,
Stephen

----- Original Message -----
From: "Dimitry Sibiryakov" <SD@...>
> >What I would like to happen is that the changes by the second user are
> >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?
>
> If the second user uses "read commited" transaction, then you can
> 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.