What some people do is have a column that increments each time there is an
edit to insure that nothing else has edited the row or certain columns in
the row. This requires a fair amount of comprehensive planning and explicit
development to insure things work properly. All processes operating on the
data must conform to the rules you specify. This is not an easy problem to
solve when you take concurrency away from the server and manage it yourself.

Jason Wharton

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of listas HRSOFT
> Sent: Friday, May 20, 2005 7:51 AM
> To: IBOBJECTS-GROUPS
> Subject: [IBO] The old value of a field
>
>
> IB 6 - IBO 4.5 registered- Delphi 7 Pro
>
> Dear Friends
>
> I'm converting a Pdox app to IB with IBO.
> In IB/IBO is not convenient to set the PessimisticLocking to true.
> I use implicit transaction in my app.
>
> How to prevent the follow situation, with the app in the network?
> - suppose that user A has the record X in editing mode, with
> the content
> of field Y='abc'
> - suppose that user B change the content of the same record X, change
> the content of field Y to 'xyz' and save the record
> - when the user A save the record in edit mode (post), the content of
> the field returned to 'abc'.
>
> How to avoid this?
>
> Thanks in advance
>
>
> Hércules Russano
> HRsoft Informática
> 0xx21-26013970 - 3246-2342
> <http://www.hrsoft.com.br/> www.hrsoft.com.br
> MSN Messenger: <mailto:hrsoftbrasil@...>
> hrsoftbrasil@...
> Skype: hrsoftbrasil