Hi, I have 0,02 NOK input on this. I have been using the unstable version for a while now, and because of a recent but unrelated problem went back to 2.0.5. That version refused to open the file with an error message approximately like "unable to parse the XML". I went back to 2.1.4, checked scheduled transactions and noted one completed "fire once" transaction. I deleted that entry and saved. Now 2.0.5 opens the file without problems. So the incompatibility is quite minor.
Reiterating on things previously said: "In version 2.1.2 the format for scheduled transactions in data files was changed. Files using the old format will be read without problems by new versions, but the new version of GnuCash only writes the new format. The new format cannot be loaded by older versions of GnuCash. (If you try, the file will fail to be loaded with an error message.) As a result, if you begin using the new Gnucash, and you have data files with (possibly completed) scheduled transactions, then these files will not be readable by older versions. Therefore, if you use or have used scheduled transactions, you are advised to make a backup copy of the data file before saving it with the new GnuCash. If you must, you can make an existing data file readable by older versions of GnuCash by deleting all records of scheduled transactions in the scheduled transactions editor." Bye, Bastiaan. Christian Stimming wrote: > Am Samstag, 16. Juni 2007 23:06 schrieb Thomas Bushnell BSG: > >>> *DATA FILE NOTICE* If you are using Scheduled Transactions, the data >>> file saved by GnuCash 2.1.2 and higher is *NOT* backward-compatible with >>> GnuCash 2.0 anymore. Please make a safe backup of your 2.0 data before >>> upgrading to 2.1.2. >>> >> This kind of announcement is extremely problematic from a >> redistributor/packager perspective (mine). But maybe it's just the >> announcement that's problematic and not the actual change it points to. >> > > As already written in earlier responses, the meaning should have been as > follows: > > >> "If you save a data file with the new Gnucash, then an old Gnucash >> will be unable to read it." If this is true, then it means that users >> who start using the new Gnucash will have committed to the new one, >> essentially, for that file, and backups are advised in case going back >> to the old Gnucash is needed. >> > > Do you have any suggestions to improve the wording in our announcements in > order to avoid further problems with ambiguous message? That would be very > helpful. > > Christian > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
