Still there. A date entry would indeed be so much more useful.
Regards, Adrien > On Oct 21, 2019 w43d294, at 9:01 AM, Stan Brown <[email protected]> > wrote: > > On 2019-10-21 09:40, Derek Atkins wrote: >> James Thorpe <[email protected]> writes: >>> >>> a) Fear of corrupting previous year's transactions >>> >>> Once my financials are done for the year and reported on, I do not >>> wish to inadvertently enter or modify a historical transaction that >>> will result in the same reports producing different results. It is >>> easy in GnuCash to enter a transaction with a date for a previous >>> financial year or, mistakenly change the date of an existing >>> transaction without noticing it. > > You can avoid that by File ยป Properties. > > Unfortunately, you have to update that property every ... single ... > day, because "day threshold for read-only transactions" doesn't let you > enter a date, only a number of days offset. So if you calculate that > today is the 294th day of the year, and set the threshold to 294 so that > none of last year's transactions can be altered, when you open your GC > file tomorrow it will allow alterations of Jan. 1 this year; the next > day Jan. 1 and 2; and so on. > > That rather odd design choice is in 2.6.x; I don't know whether it's in 3.x. > > > -- > Regards, > Stan Brown _______________________________________________ gnucash-user mailing list [email protected] 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.
