> On Aug 1, 2018, at 2:20 PM, aeneas <recei...@gowdygroup.net> wrote: > > Well now, I'm glad I asked. The referenced links do provide useful details > that I didn't know and that does look useful. > > I probably should have included a few more facts which follow: > - OS: Windows 7 > - GNUcash Version: 2.6.15 (I believe for more than a year) > - Data format: File (SQLite) > It looks like the current version is 3.2 and apparently the last of version > 2 was 2.6.21. > > I've decided that using the PortableApps version of GNUcash has some appeal. > One factor is that it is pretty easy to setup a new jump drive when it comes > time to migrate. This allows easy path to a new release that has no affect > on current operational version. Also, based on information learned from the > referenced links (above) it looks like the PortableApps version has done a > very nice job of locating all of the applicable data within the folder > structure used for GNUcash Portable. I was able to copy my SQLite DB file > to what looks to be the GNUcash preferred location and open it without any > problem. > > That's all been real nice. However, my question comes from the fact that I > have enough experience in data processing to know that the kind of issues > I'm concerned about don't necessarily reveal themselves instantly. > Furthermore, with this type of application it doesn't take very long to > become very invested in the new version and the idea of going back to the > prior release becomes a major problem to do correctly. Thankfully the prior > version, in this case, is sitting there completely undisturbed because of > using portable GNUcash. > > Therefore, I'm thinking there may be some merit to following a particular > path when undertaking a migration such as this. For example, what about the > following ideas: > - Is there any merit to the idea of making a conversion to Version 2.6.21 > prior to converting to 3.2? > - Is there any merit to choosing a different data format, such as XML, to be > used for migration purposes? > Sorry to be a bother but this does seem to me to be a subject that everybody > using GNUcash ought to be concerned about. >
There’s no advantage to upgrading to 2.6.21 before upgrading to 3.2. It’s also unlikely that using XML instead of SQLite3 would make a difference, but in that case there’s no harm in doing a save-as to XML for safety. That aside, you should be aware that with 3.x GnuCash has changed the location of some of its configuration and auxiliary files to match each supported operating system’s conventions. Another user has reported that Portable hasn’t made the corresponding adjustments and so 3.x is apparently somewhat broken with Portable. You might search the mailing list archives for details. Regards, John Ralls _______________________________________________ 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.
