> >(when someone starts editing, we explicitely do 'update
> >{tablename} set id
> >= id where id = {value}' -- this conflicts with parent
> >records already being edited.
> NOWAIT is correct for this - all the app has to do is catch the lock
> exception and tell the user that someone else is already
> updating this set of data.

And what would be the best course of action if the application wants to
permit the user to make that update anyway? The obvious answer is
probably a 'hard refresh', meaning close the dataset, commit the
transaction, reopen the transaction, reopen the dataset, and retry the
operation.

But is there something easier? Will a refresh of the current (modified)
row do?

Thanks in advance,
Salam,
sugi.