Re: Error 3218 - could not update - record locked
the trouble with locking records is JUST what you have described. The idea is to retain locks for the minimum period of time, and not to keep locks for an extended period
"No locks" is a bit of a misnomer. What it ACTUALLY does is rereads the record before updating the change. If it changed since it first read it, it reports the change to you - if it hasn't changed, it just writes your change.
So you get the benefit of both worlds - safe updates, without locking users out.
I am not 100% sure, but even if you have single record locking, the dbs may actually lock several records at the same time, because I think it has to lock the entire page/cluster on which the selected record resides - so it ALSO locks neighbouring records. (I think!)
Gemma was my dog
if a poster helps you, please click the scales at the top right of this posting, or use the thanks button alongside.