I suspect you will find some orphaned transactions in between the ar,
ap, gl, and acc_trans tables in the database. By that, I mean there
will be transactions in acc_trans which are no longer referenced by the
other tables. Unfortunately, until more of the business logic is moved
to be in the database, this will continue to be possible area for
problems. It is resolvable but it takes a little work. I spent some
time writing sql queries to find & resolve the offending transactions.
Generally, the offending transactions were left overs (duplicates) from
deleted/replaced transactions and therefore could simply be deleted.
Trevor
Ole Holte Sandvik wrote:
Thanks Pete.
I will upgrade and see if it does the trick.
If not, I will select another account chart and see if it helps. If that
doesn't help I guess I will seriously have to reconsider my accounting
skills... ;-)
Thanks again,
Ole.
På Tue, 12 Feb 2008 11:02:48 +0100, skrev Pete Houston
<[EMAIL PROTECTED]>:
Hello Ole,
This sounded strange, so I have just run a test with my data. I have to
report that I do not see the errors which you describe. The income for
the year is the same regardless of whether it is the actual year or the
comparison year in the report. This is the case using version 1.2.12.
Pete
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ledger-smb-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ledger-smb-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
