On 12/19/2023 10:40 AM, Kalpesh Patel wrote:
Thank you, for being flameless. My ears are all yours to listen to the
explanation...
I actually didn’t tell the whole story ... I did software development for good
chuck of my early career in the computer field (worked with through
MIL-STD-2167/A when it was de-facto).
I am concurring that DATA is in a file of "program data" that gets read in when the "program"
starts and that the "change accounting period" function changes this data. I am not sure I concur that to get
it to take effect the program has to be shut down and start again manually. During the input phase of the change, upon
confirmation "click" a call to start again just that portion of the program is doable, IMHO. It may require
implementing a different sub-routine or sub-function if the existing one is not sufficient to do so.
Quite so, could (without closing and reopening) change the value the
program would use for any NEW reports, etc. that were run (mew = post
change). But remember, gnucash saves what reports were open (in other
words, if I had an "Income Statement" and "Balance Sheet" on the bar,
they are still there when I reopen. Some of which could have been
dependent on "current accounting period"
BTW -- this calls for a test, because I think we don't necessarily know
WHAT got saved for those pre-existing reports. I am always using
absolute dates in reports, and I know THAT gets saved. But has gnucash
converted things like "current accounting period" to actual dates when
it runs the report. In other words, the details of how "open" reports
are saved. In other words, depending on what saved, even save,
close,open might not work.
Michael D Novack
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
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.
