Hi, I have 2 recs after applying filters. Find(’-’) shows me the first. Next = 0 immediately after that returns TRUE. The problem is that system steps into the second record, BUT the TRUE value of NEXT = 0 triggers the EXIT function. This particular situation occurs in k22. The problem is not “stable” - if the code is triggered from the other place (caeteris paribus), everything is ok. Has anyone met such a strange behaviour?
Is this happening in the ApplyItemLedgEntry function in codeunit 22? Is your database SQL? I have just recently seen this happening in this function. I also believe this to be related to SQL but can’t be certain because of the difficulty in reproducing the error; as you indicate the problem is not stable. I’m basing my belief on the fact that I have a SQL database where the problem occurs and if I do a backup/restore of this database into a Navision database the problem does not happen.
What Navision version does this happen in ?
Hi, this is 3 60 SQL Database. The Trigger is really ApplyItemLedgerEntry.
There has been a fix to a problem related to NEXT in one of the later 3.60 hotfixes released approximately 1 year ago. Perhaps obtaining the latest c/side binaries will help you. This fix was in ndbcs.dll, but you’ll also need a new finsql.exe. If you already have these then you are hitting a new problem apparently.