Rather than renaming the current working file I suggest using File > Save As to save it with the new name (make sure you are saving to the right directory). Then when you open Gnucash the next time it will automatically re-open that file.
Colin On 9 August 2017 at 20:41, Denis_gmail <dlap...@gmail.com> wrote: > No wonder I was confused! Really appreciate your help and explanations of > what went wrong. > Just to be on the safe side I'll make a copy of all those files before > deleting. > > Thanks again > Den > > > > Le 2017-08-09 à 13:37, Buddha Buck a écrit : >> >> You probably also have a "den.gnucash", a >> "den.gnucash.20161107142750.gnucash", a >> "den.gnucash.20161107142750.gnucash.20161201140745.gnucash", and a >> "den.gnucash.20161107142750.gnucash.20161201140745.gnucash.20170208132409.gnucash" >> as well. >> >> When you are using GnuCash to work on the file "foo.gnucash", GnuCash will >> periodically save a backup file with the name >> "foo.gnucash.<timestamp>.gnucash". It is easy to get lots of these backup >> files with varying timestamps in your data directory. >> >> If you open up the backup file instead of your original data file, so you >> are working on "foo.gnucash.<timestamp1>.gnucash", GnuCash will create >> backup files with the name >> "foo.gnucash.<timestamp1>.gnucash.<timestamp2>.gnucash". If you decide to >> use that backup file instead of either your original data file or the first >> backup file, you'll get three timestamps in the filename. It appears that >> you ended up working on the backup of the backup of the backup of the backup >> (for a total of 4 timestamps). >> >> This can be a problem if you have been putting transactions into the >> original file after you first started using the backup file instead. In that >> case, there are unique transactions in two different files that have to get >> (manually) merged. >> >> If you are satisfied that the >> den.gnucash.20161107142750.gnucash.20161201140745.gnucash.20170208132409.gnucash.20170209101150.gnucash >> file is complete and accurate, then I would suggest renaming it to something >> simpler (like den2.gnucash) and deleting all the other gnucash files that >> are confusing things. >> >> There is a setting that controls how often it makes a backup, and how long >> it keeps them around. >> >> >> On Wed, Aug 9, 2017 at 1:24 PM Denis_gmail <dlap...@gmail.com >> <mailto:dlap...@gmail.com>> wrote: >> >> There is something I don't understand in the file names used by >> GnuCash. >> >> I must miss something...:-( >> Today I save the file as usual when exiting (today is >2017-07-20< and >> the file name used by GnuCash was:) >> >> >> den.gnucash.20161107142750.gnucash.20161201140745.gnucash.20170208132409.gnucash.20170209101150.gnucash >> >> What is even more strange is the fact that this file name NEVER >> change. >> It's always the same and not related to the date. >> >> Any comments ? >> >> Den >> _______________________________________________ >> gnucash-user mailing list >> gnucash-user@gnucash.org <mailto:gnucash-user@gnucash.org> >> https://lists.gnucash.org/mailman/listinfo/gnucash-user >> ----- >> 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 > https://lists.gnucash.org/mailman/listinfo/gnucash-user > ----- > 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 https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.