I'm not sure this happened prior to version 3. I constantly update reconciled 
transactions. I'm not altering the values, just the reference number (in the 
NUM field) or the description. It cannot possibly be sensible that adjusting 
descriptive, or reference, data in a reconciled transaction leads to its being 
unreconciled, with all the chaos that then ensues. The reconciliation is to do 
with the values, not the description or reference.

-----Original Message-----
From: gnucash-user 
<gnucash-user-bounces+anthony=gardensmontessori....@gnucash.org> On Behalf Of 
Adrien Monteleone
Sent: 12 August 2018 17:48
To: gnucash-user <gnucash-user@gnucash.org>
Subject: Re: [GNC] Reconciliation being undone without warning

Editing a reconciled transaction sets the status to ’n’. That is intended 
behavior.

Concerning the warning dialog you either told it not to warn you for the 
session, or forever. If closing and restarting GnuCash doesn’t bring back the 
warning, check the Actions > Reset Warnings dialog and you’ll see it there. You 
can check the box for it and Apply and it will show next time you edit a 
reconciled transaction.

Regards,
Adrien

> On Aug 12, 2018, at 7:19 AM, Anthony Marrian <anth...@gardensmontessori.com> 
> wrote:
> 
> What a prat I am. Sorry: from y to n
> 
> From: Colin Law <clan...@gmail.com>
> Sent: 12 August 2018 11:32
> To: Anthony Marrian <anth...@gardensmontessori.com>
> Cc: gnucash-user <gnucash-user@gnucash.org>
> Subject: Re: [GNC] Reconciliation being undone without warning
> 
> On Sun, 12 Aug 2018 at 11:07, Anthony Marrian 
> <anth...@gardensmontessori.com<mailto:anth...@gardensmontessori.com>> wrote:
> I'm running version 3.2. I reconciled a bank account to the end of July, and 
> then added voucher numbers (in the NUM column) to a number of the 
> transactions, as I have habitually done with all versions before 3. No 
> warning appeared, BUT I have just noticed when trying to reconcile July that 
> the all the transactions which had numbers added to their NUM field also had 
> their reconciliation flag moved from n to y. I imagine this behaviour is not 
> by design.
> 
> If it is now y then they are still reconciled, or do you mean they changed 
> from y to n?
> 
> Colin
> 
> 
> Best wishes - Anthony
> _______________________________________________
> gnucash-user mailing list
> gnucash-user@gnucash.org<mailto: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.
> _______________________________________________
> 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.
> 


_______________________________________________
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.
_______________________________________________
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.

Reply via email to