Corrupted reconciliation cannot be fixed?

[David T.]

Ken,

I think there’s a misunderstanding here. Reconciliation is a *going forward* action. That is, you reconcile an account as of a particular date—and once you’ve reconciled, in most cases, you won’t be going back to change transactions that you’ve reconciled. (There are circumstances in which past transactions can be—or become—altered, some of which are documented in the Guide Chapter 4.5)

The point is, you shouldn’t have finished your March reconciliation (indeed, GnuCash tries to keep you from finishing your March reconciliation) until the transactions in your accounts matched those in the account statement you were reconciling against. And if you *did* finish the process, then the accounts ought to be good going forward. 

Perhaps you need to explain further how (and why) your previously-reconciled accounts would need alteration. I think that might help explain why you are getting into trouble during subsequent iterations of this process.

David

On Jul 18, 2015, at 9:40 AM, Ken Heard <kenslists at teksavvy.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 2015-07-17 22:31, John Ralls wrote:
> 
>> The reconcile dialog isn’t modal and live-updates. When I find that
>> I missed posting something I just switch back to the register and
>> create the transaction, then switch back to the reconcile dialog
>> and reconcile it.
> 
> I tried that. but it did not work.  I noticed the problem when I
> started the April reconciliation and wanted go back to the March
> reconciliation to correct it.  I exited the April reconciliation using
> "postpone" option rather than "cancel".  The March reconciliation was
> consequently locked in, with the "forever" result I described.
> 
> That was the reason for my suggestion always to use "cancel" rather
> than "postpone" to create or change transactions in the register
> during the reconciliation process.  That way the previous
> reconciliation can be changed if necessary.  The only disadvantage to
> using "cancel" is that the check offs all have to be done over again
> - -- a minor inconvenience in view of the situation created by using
> "postpone" instead as described in my original post.
> 
> Regards,
> 
> Ken Heard
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> 
> iEYEARECAAYFAlWqVzsACgkQlNlJzOkJmTclWACfW7NWo8u4mKsMyhOICNHW+kOc
> qTUAmQE01BPdjvd6mMStEJ6qWIxmaV5q
> =HRoJ
> -----END PGP SIGNATURE-----
> _______________________________________________
> 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.