If I understood David correctly, the error was not caused by the change in the reconciliation code, but by David inadvertently entering a short year date. (“20” instead of “2018”, which became “2020”)
In that case, since there is no facility to the user to edit reconcile dates, the only option is to edit the data directly. Regards, Adrien > On Apr 9, 2020 w15d100, at 1:10 AM, D via gnucash-user > <gnucash-user@gnucash.org> wrote: > > So, David, you're saying you edited the data file directly in order to fix > the new reconciliation problem? > > If so, that's a pretty strong indication to me that this change should get > rolled back. There is no situation in which I think an end user should have > to edit the data directly in order to complete reconciliation. > > David T. > > On Apr 9, 2020, 06:55, at 06:55, David Cousens <davidcous...@bigpond.com> > wrote: >> Problem resolved. Caused by entering 31/12/20 instead of 31/12/2018 >> when >> entering the end date fro a previous reconcilation. Edited datafile and >> corrected all reconciliation dates set as 2020-12-31 to 2018-12-31 and >> the >> file now reconciles correctly to 31/12/2019 with the correct starting >> balance calculation, >> >> David _______________________________________________ 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.
