Lock time out and Transaction not rollingback completly <- URGENT

Hi,

Going thru the inventory and error log of our application I notice that
sometimes (not always) when a Lock time out error occurs the transaction is
not rollback completly. Meaning that all changes are rollback sucessfully
exept the one done on the table that throwed the lock time out.

I'am not able to reproduce the error since I don't know how to force a lock
time out to pop up but I can assure you that the change were apply to the
table a not rollback.

Is this a know issue? Is there any way to fixe this? It's really urgent
because it is altering our live inventory.

Setup is Nexus 1.07 with all the hotfixes applied. Server is accessed over
tcp/ip with >50 clients connected at all time.

I'd be happy to post more info if needed.

Thank you.


--
Regards from Quebec.

David Charron

David Charron wrote:
> Going thru the inventory and error log of our application I notice that
> sometimes (not always) when a Lock time out error occurs the transaction is
> not rollback completly. Meaning that all changes are rollback sucessfully
> exept the one done on the table that throwed the lock time out.

Are you calling Cancel on the table? When there is an exception, you
need to roll back the transaction and call TnxTable.Cancel. If you don't
do the latter, the edit is still active and may be posted, e.g., if you
move to a different record.

--
David Marcus [NexusDB Expert]

David Marcus [NDX] <David.Marcus@ndx.nexusdb_x.com> wrote in
<MPG.1b84280ac927573e989958@news.nexusdb.com>:
>Are you calling Cancel on the table? When there is an exception, you
>need to roll back the transaction and call TnxTable.Cancel. If you don't
>do the latter, the edit is still active and may be posted, e.g., if you
>move to a different record.
>

That must be it then. I'll try it and keep you posted.



--
Regards from Quebec.

David Charron