It seems that there always exists a possibility that data base/file structures can change from one version to another of GNUcash. Generally speaking developers try to consider this and may make accommodation for some older versions in newer versions of their software which means there is a chance that newer versions of the software will function properly when using data bases/files produced by older versions. However, when needing to migrate backward from a newer version to an older version this is likely to be more problematic. The nature of the data bases/files that GNUcash is producing is such that failure to do this properly risks the creation of serious problems when making such migrations. This owes to the notion both that the data consists of financial records as well as the idea that a large amount of data accumulated over a long period of time may be involved.
Therefore it would seem that changing the version of GNUcash is something that needs to be done carefully. This should include some means to verify success in a short amount of time insofar as it doesn't take long before the idea of returning to a prior state known to be good can become extremely difficult if not impossible. Is there a procedure that ought to be followed when making such a change? What is the possibility that these considerations differ based on the chosen output format? -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html _______________________________________________ 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.
