On 8/9/20 5:25 AM, bengt...@gmail.com wrote:
> Would like to revive this old thread since the request made by the OP is
> still valid for us Swedish users (and maybe German users according to one
> post in the thread?). I wonder if there has been some development along
> making transactions "persistent" or read-only/locked/un-changeable? 

When I started using GNC, about 5 or 6 years ago, I had 2 surprises: 1) I 
didn't have to enter the earliest transactions first as I was trying to find 
the old transactions for the assets/liabilities while I was entering daily 
transactions.  And 2) that I could edit entered transactions.
I grew up in the pen and paper era so that editing an entry was a no-no but, 
since my current effort was not for other people, it was great as Idon't make 
mistreaks! Yeah! Right!  (For those of you, myself included, that didn't catch 
the irony of that remark. I do make many mistakes.)
The idea of freezing a transaction at some point is an idea that would be 
appreciated, even by a user like me.  Just before I retired,  There have been 
times that I accidentally changed a transaction that I didn't intend to. I 
found that (some of) the commercial programs could allow someone to change 
transactions - at least by a supervisor.  I retired because 1) I didn't want to 
learn a system that did not use account numbers and 2) I was confused by having 
as many as five different accounts with the same name - one in each of the 
top-level accounts.

Thank you guys for all you have done with this program.  

Bruce
 Preach the Gospel wherever you go.
 If necessary, use words.
_______________________________________________
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