> The problem is not that the record is in use.
>
> The problem occurs when the record has been committed and an
> update occurs that overwrites that record without warning.

If you want the warning then you need to use the transaction isolation that
provides it. tiCommitted will not provide such a warning if the record has
been committed already.

You can't have your cake and eat it too...

Jason Wharton