I think I saw a similar problem when a subroutine reopened an opened File. This caused all the Record locks to be dropped and as the records were not locked to the isolation level, this caused a fatal. It was painful to track, even using the error clauses, the program fataled without going through the error clause leaving no messages to track the problem. Worse was the cause was far removed from the section of code where the fatal occurred.
David Jordan Managing Consultant [EMAIL PROTECTED] DACONO Holdings Pty Ltd www.dacono.com.au > On 12/23/05, Serguei <[EMAIL PROTECTED]> wrote: > > From time to time when the Basis code executes COMMIT statement on Universe > > the program breaks with the message: > > > > FATAL: Corrupted item in the transaction cache. > > Rolling back uncommitted transactions begun within this execution > > environment. > > FATAL: Corrupted item in the transaction cache. > > > > What this could mean? ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
