Actually, related to this: Is there a straightforward way to try a version without having to go through a complete installation on Windows and without disturbing the existing installation?
If it's possible then I could run 2.6.last and then 3.x stand-alone with a test copy of the file before jumping to 4.x and committing to the full install. On 2021-10-02 15:11, AC wrote: > I agree don't upgrade if not absolutely necessary but I will likely be > replacing this computer in a few months so starting from a newer > installation is much more likely to happen in that case. > > So you're saying I should be able to do three stages of 2.6.last, > 3.x.last and then 4.x.last? > > Are there any big changes to basic functionality from 2.6 to 4.x? I'm > making my way through the change logs but a lot of it is related to > various features I don't use (at least that which I've read thus far). > > > On 2021-10-02 15:06, Derek Atkins wrote: >>> From 2.6.3 you will need to jump to 2.6.last, then 3.x, then 4.x >> >> At every version you should load your data file and then save it. >> >> While there is no requirement to upgrade, and "if it ain't broke, don't >> fix it" may apply, if you have a system crash and need to rebuild your >> system, it'll be easier to use recent versions. >> >> -derek >> Sent using my mobile device. Please excuse any typos. >> On October 2, 2021 5:56:23 PM AC <gnuc...@acarver.net> wrote: >> >>> Ok, I've been running along on 2.6.3 on Win 10. No issues to date that >>> I can see. >>> >>> I know there's been various changes throughout the rest of the 2.x and >>> 3.x series and we're now on 4.x which sparks some questions: >>> >>> >>> Do I really need to update? I only use the basis ledgers for standard >>> banking accounts, credit cards, loans, mutual funds; scheduled >>> transactions; and basic reports (typically just the standard transaction >>> report when I need a list for taxes). I don't use online transactions, >>> imports, or business features. Can I assume that the basics still work >>> the same way? >>> >>> If it's better for me to go ahead and update how painful will it be to >>> update? >>> >>> I recall some suggestions previously about upgrading in increments and >>> if that's the case how many increments am I going to need (hopefully not >>> one for every point version)? >>> >>> _______________________________________________ >>> 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.
