Thanks Geert, Windows 7. I found the file in C:/Users/TOSHIBA/.gnucash/saved-reports-2.4. Out of curiosity, I looked for it on my Windows 10 computer and didn't find it. I didn't see anything special for Windows 10 in the wiki. Not important really as long as the update takes care of that.
You said, " If you want to force the migration, you should move the directory aside before running gnucash 3.x." Will it work to copy the 2.4 file to the 3.4 directory? I saved the 2.4 file from the working pc to a USB. I'm guessing I'll have to delete the 3.4 saved reports file, if it even exists as I have not saved any reports on the test computer. I would like to give it a try. Roger -----Original Message----- From: Geert Janssens <geert.gnuc...@kobaltwit.be> Sent: Tuesday, March 19, 2019 11:43 AM To: gnucash-user@gnucash.org Cc: rmom...@gmail.com; 'John Ralls' <jra...@ceridwen.us> Subject: Re: [GNC] Saved report configurations Op dinsdag 19 maart 2019 18:08:29 CET schreef rmom...@gmail.com: > Version 2.6.17 > > I looked at the wiki and am not sure where to start. If possible, just > need to know: > > What is the name of the file where the saved report configurations are > stored? > Should those saved configurations be available when I update versions? > > Thanks, > Roger > The file is called saved-reports-2.x where 'x' depends on your gnucash version as does its location. For 2.6.17 the filename will be saved-reports-2.4 and it will be stored in DOT_GNUCASH_DIR as described for your OS (which you haven't provided yet) under https://wiki.gnucash.org/wiki/Configuration_Locations#DOT_GNUCASH_DIR For GnuCash 3.0 and up the file will be in https://wiki.gnucash.org/wiki/Configuration_Locations#GNC_DATA_HOME for your OS. GnuCash will look for a file named saved-reports-2.8 first in there and if missing it will try to open saved-reports-2.4 in the same directory. As for updates, if you update gnucash from 2.6.x to 3.x it will copy these saved reports from the old location to the new one for you, but only if the new location didn't exist yet! So if you ran tests on your new PC with only 3.x and then install 2.6.x on that system, the migration will not run again after upgrading to 3.x. If you want to force the migration, you should move the https://wiki.gnucash.org/wiki/Configuration_Locations#GNC_DATA_HOME directory aside before running gnucash 3.x. Regards, Geert > -----Original Message----- > From: John Ralls <jra...@ceridwen.us> > Sent: Tuesday, March 19, 2019 10:43 AM > To: rmom...@gmail.com > Cc: GnuCash <gnucash-user@gnucash.org> > Subject: Re: [GNC] Saved report configurations > > > On Mar 19, 2019, at 9:33 AM, <rmom...@gmail.com> <rmom...@gmail.com> > > wrote: > > Where are the saved report configurations kept. Apparently they are > > not part of the GnuCash data file. I installed vs 3.4 on another > > computer to test it and opened the data file transferred via USB. > > The saved report configurations are not there. Found one file that > > may be where they are stored, same name as the data file with the > > extension .LCK > > It depends on what operating system and GnuCash version, see > https://wiki.gnucash.org/wiki/Configuration_Locations. > > 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. _______________________________________________ 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.