On Sat, 9 Feb 2019 at 11:23, Michael Hendry <hendry.mich...@gmail.com> wrote: > .. > My guess is that GC is setting up all of my Scheduled transactions (“B” > lines) and then rolling them back (“R” lines) without committing them. > > There follows a series of four empty START-END pairs at line 643. > > This is then following at line 651 in the earlier file (on the right of the > screenshot) the one transaction scheduled to take place on the 8th of > February - but involving a Commit, then a Begin then a Commit. > > Today’s file (on the right) starts at line 651 with the same transaction and > the same Commit-Begin-Commit sequence, and then goes on to record the > scheduled transaction due for today. > > Each file ends with an orphaned “D” line, whose UID doesn’t appear earlier in > the file. > > This may be the expected behaviour, but it seems odd to me!
That looks very similar to what I am seeing with 3.4 on Ubuntu. Colin _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
