This is an update of sorts of a long series of messages here since I had an issue with saving my transactions at the end of July.

I was unable to copy and send GNU files to the kind people who tried to help me. I have no idea why, copy and paste after changing to the file type required just did not work.

There were many messages concerning why I seemed to have more than one set of GNU files with  different user names, and at different times.

I have now downloaded all the files containing "GNU" for the period of July 2023.

There is bewildering list with an equally bewildering number of names, suffixes, etc., such as -

16  files of type  - gnucash.trace.YXDV81.log each one duplicated and where only the alphanumeric is different

A large number of 'shortcuts' and many files which I think are backups with several date strings in the same file.

I have not been able to decipher these nor files with .msf or .gcm or .dmp or GnuCash_is1 !!

Maybe I have made numerous errors, and unwittingly put files in different places or formats, but..... I am a longtime user of GNU, most of the current longer files start with GNU FEB 12 2019.gnucash.....

Finally, all the files I have now are in Documents (C:\users\administrato) with various sub-addresses. That seems to have sorted the issue with one of the issues raised in a message -

"Be sure you aren't confusing the two users on your system! (one is "Barry Mahon" and the other is "administrato""


Any help at this stage would be welcome. I have a tax declaration to do by mid November.

I would be willing to start all over again and re-enter the 2022 transactions, the tax year concerned, and create a new 2023 set of transactions to continue.

Finbar


_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
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.

Reply via email to