Geoff Rees wrote:

> Hi,
> [using IB6.0x]. We have the situation that often the same record is selected by 2 computers at approx the same time. One computer is used to update 2 fields, the other computer another 2 different fields. If the first computer saves (commits) the records while the other computer is still active on the same record, then the data will be lost that was entered via the first computer when the second computer commits. (hope that makes sense).
> What is the solution? Can you lock certain fields?
>
> Thanks for any help
> Geoff
>
>

Hellen Borrie did an excellent job of explaining the way the database engine itself works so I wont attempt to repeat her explanation (she does it better anyway).

My suggesting may be easier said than done however I might as well suggest it.

If in this particular application you have a certain table that is hit with conflicting updates to different columns to the same row of data, it may be that
those different columns are in fact independant and unrelated from each other and could fit into 2 seperate tables with the same primary key column.

This way the updates would occur to 2 seperate rows in 2 seperate tables.

If the updates are willy nilly to arbitrary columns of the same row, then this wont work (short of breaking out each and every single column into its
own table, which is of course possible in necessary)

Can you share with us what kind of application this is?