Helen Replied:

>Set PessimisticLocking true on the dataset. As soon as the user attempts to
>go into Edit mode (a client-side concept) the application will send a
>"dummy update" to the server, thus either a) acquiring a write lock for
>that record for that transaction or b) denying the lock >because some other
>transaction already has a write lock on the same record. If the lock is
>denied, IBO won't let the dataset go into Edit mode.

>Obviously this only works if a) the transaction is read/write and b) the
>dataset is also set RequestLive true (or its equivalent for multi-table
>sets).

>Helen

Yep.. but is there a way to get a notification that somebody is busy with
the record, and more importantly who is busy holding up the record.
I have the problem that users go and have coffee with the recordset still in
edit state, preventing any edits until they return.

Regards

Adrian