Vlad Horsun wrote:

> Did you change an error number or error message only ? Or you added
> new secondary error code ?
>

The error message was changed, but a new secondary code may be better
for compatibility with old clients.

>
>> With the transaction number and the MON$ tables, an admin could know the
>> connection which is blocking the record.
>>
>
> Only if this transaction still active when admin decide to do something
> with it. Highly unreal scenario i think.
>

Not unreal if the transaction commit depends on user action.
One may have forget to close a isql session, for example.

That may be more interesting when an admin could delete records from
MON$TRANSACTIONS and rollback others transactions.


Adriano