>Hilmar,
>Yes, I would be rlock()'ing the account record.
>
>Currently my app only has error handling to the point of tracking the errors to a table.
>
>It appears I will need to expand my error handling to handle update conflicts, something I have worried about anyway. I have found a thread by searching for "quantity on hand". Just started reading it. Will see if that offers details. Also have some white papers on multi-user programming and am re-reading them as well.
>
>Thanks again,
>John
IIRC, a transaction will lock records modified during the transaction automatically. But I don't know how error handling will work in this case, and explicit locking might very well be the simplest route.
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)
