kriki wrote:
...
The only way to find out is to use the debugger and following every write to the G/L Entry table (you can start to debug every time codeunit 12 is entered (this is the one that writes to the G/L Entry.
BTW: another way to help you debugging: if you are on SQL, you can try this trick: just before the COMMIT that generates the error. Do a FINDFIRST on the G/L Entry to force NAV to write all records it has in the buffer to the table. Then add "IF NOT CONFIRM('Continue?',FALSE) THEN ERROR('STOP'); The CONFIRM waits for a confirmation before doing the COMMIT. Opening another session you can see what this session has written in G/L Entry. DON'T DO THIS IN PRODUCTION BECAUSE YOU ARE BLOCKING EVERYONE!
or a MUCH better way would be to search mibuso for Rashed's trick to solve this.