Multi-currency transactions with trading accounts from 2.4.13 getting messed up in latest 2.6.3

[David Carlson]

On 6/19/2014 10:06 PM, Mark wrote:
>    Hello,
>    I am having problems with my old gnucash files and some of the
>    multi-currency transactions in those files.
>    I am using trading accounts and have transactions with USD and EUR
>    accounts that handled through respective trading account splits.
>    So far, I was using 2.4.13
>    I just installed 2.6.3 on a new machine and loaded the old gnucash
>    files.
>    Some of my transactions now have a 5th split with one of the IMBALANCE
>    accounts (EUR or USD) added and one of the amounts of the trading
>    amounts messed up.
>    Loading the exact same file into 2.4.15 works fine (exactly as in
>    2.4.13).
>    What could be the problem here? Is this a known issue? If not I will
>    send a sample transaction...
>    Thank you...
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>

There has been a problem with some scheduled transactions getting
corrupted when they are created by the since last run assistant in the
2.4 series.  I personally have seen this with reinvested dividends in my
case.  The only clue I saw was that if a corrupted transaction was
manually edited sometime after it's initial creation, it could go out of
balance, which would really stand out if trading accounts was active.  I
have been told that the problem has been corrected in the 2.6 series,
but I have not upgraded yet to confirm that.

The underlying error is not visible in the register view.  It has been
reported as https://bugzilla.gnome.org/show_bug.cgi?id=731019.

You may be seeing another manifestation of that bug, which will not be
fixed, as the 2.4 series is no longer supported, and so far, has not
been seen in the 2.6 series.  If so, I suspect that you may need to
manually delete and  re-enter those transactions in either version of
GnuCash, taking care not to accept any autocompletions, which can
propagate the problem.  That is fairly easy to try if there are not too
many of them.  I only had 29 bad transactions by the time I identified
the problem.

David C