Re: Logical log usage and long transactions

From: "Alnis Bajars" <alnisb@colorcorp.com.au> >We have some old data entry screens (whose logic flow is quite hard to >understand) giving us "Long transaction aborted" errors on a couple of >occasions recently. > >In one instance, it occurred in a Stock Transfer screen, after a user moved >quantities of six stock items from one warehouse to another. Hardly the >sort of transaction activity to generate a long transaction, I would have >thought. The code wraps the header and detail sections entry Huh? >My question is: does this error really mean what it says, and I should >shut >up and just work out whatever screwy logic is causing this. Or, is there >some insidious process going on that, if I was aware of that process, would >get me faster to the point of resolution of this issue. Any insights that >might help me resolve this would be gratefully received. Well, does the process look something like this: BEGIN WORK INPUT.... COMMIT WORK ? If so, restructure the process so that all INPUTs are done and finished with before the COMMIT WORK is issued. HTH. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com