Thanks Hilmar,
True, our current message should say something else - but saying what you propose won't be true either, because the record IS saved, and that was what my main question was about.
OTOH, do you have any scenario when the tableupdate(), in the specified conditions, might return false?

>I don't know, really, why you have this behaviour. But let me point out that TableUpdate() can return .F. (and, pressumably, has failed!) for a number of reasons, not only update conflict with another user.
>
>This really only affects your message to the user, which might read: "For some reason, the record could not be saved". For a more detailed analysis, use aerror().