I recommend: use it only as a temporary solution.
The main problems with RLOCK() (equivalent to LOCK()) seem to be 1) the unnecessary network trafic (records are locked even if the user later decides to discard them), and 2) another user might be locked out of a record, even if the first user is only
looking at a record. Or else, you provide a button to "enter edit mode" - an additional inconvenience for the user.
Hilmar.
>As I thought about this one... even though it's old fashion, it seems to be an ideal settings for me. I mean it would only allow ONE USER to edit it, regardless how powerful our development tools are today. When a second user trys to edit an open record, PING "Sorry, another time." Like I said, I haven't used OLDVAL(), CURVAL(), etc, so I don't know what those really does.
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)
