>Hi guys!
>
>Does any body know where may I find an article on row level locking under Client/Server Enviorments?
>
>Maybe with a sample of a case where user A cannot access record Number 31 because user B is currently using it with read/write intentions.
>
>Thanks in advance.
>
>NJM
I understand the usual approach is to use optimistic buffering. This can be used with local views, too, and it is usually recommended to do so.
The user can do any change; only when trying to save the record will the database server check whether there is a conflict with another user.
Some related commands: CursorSetProp("Buffering"), CurVal(), OldVal().
Saludos, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
