Re: [GNC] Cannot write to file a new wrinkle

2023-07-30 Thread Adrien Monteleone
Thanks Michael, those are fair caveats to my recommendation. I shall 
endeavor to remember that and not assume folks only keep GnuCash data 
and nothing else in a particular folder.


Regards,
Adrien

On 7/30/23 9:37 AM, Michael or Penny Novack wrote:
BE CAREFUL --- this control of a resource by having the existence of a 
lock file indicate "resource in use" is a VERY common solution to 
restricting use to "a single concurrent user" (allow multiple sequential 
access but not multiple simultaneous access). OTHER applications might 
be creating .lck files besides gnucash. So...


1) Delete "any" .lck files only if you have your gnucash files in a 
directory reserved for just the.


2) Otherwise --- before deleting a .lck file make sure it is not a lock 
file from some other application.


___
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.


Re: [GNC] Cannot write to file a new wrinkle

2023-07-30 Thread Michael or Penny Novack

On 7/30/2023 8:13 AM, Adrien Monteleone wrote:
Also, verify that GnuCash is not running, then check to see if you 
have any files ending with a '.lck' extension in that data folder and 
delete those. (but reply back with their file names first) 


BE CAREFUL --- this control of a resource by having the existence of a 
lock file indicate "resource in use" is a VERY common solution to 
restricting use to "a single concurrent user" (allow multiple sequential 
access but not multiple simultaneous access). OTHER applications might 
be creating .lck files besides gnucash. So...


1) Delete "any" .lck files only if you have your gnucash files in a 
directory reserved for just the.


2) Otherwise --- before deleting a .lck file make sure it is not a lock 
file from some other application.



Michael D Novack


___
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.


Re: [GNC] Cannot write to file a new wrinkle

2023-07-30 Thread Adrien Monteleone
Also, verify that GnuCash is not running, then check to see if you have 
any files ending with a '.lck' extension in that data folder and delete 
those. (but reply back with their file names first)


Regards,
Adrien

On 7/30/23 7:06 AM, Adrien Monteleone wrote:

That means you have opened GnuCash with a new blank file.

I'd go recover that 'offending file' pronto!

(note, the one you gave a file name for ended in .gnucash which is a 
book file, and it might have been your current active file)


Once you've resolved that, please report back the full name of the file. 
(file path not needed)


And while you're doing that, do you have any other '.gnucash' files in 
that folder/directory?


If so, can you provide a screenshot of Windows Explorer showing the list 
of files? (be sure to use the 'full details' view so we can see file 
creation and modification dates. You might need to 'turn on' one or both 
of those columns')


___
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.


Re: [GNC] Cannot write to file a new wrinkle

2023-07-30 Thread Adrien Monteleone

That means you have opened GnuCash with a new blank file.

I'd go recover that 'offending file' pronto!

(note, the one you gave a file name for ended in .gnucash which is a 
book file, and it might have been your current active file)


Once you've resolved that, please report back the full name of the file. 
(file path not needed)


And while you're doing that, do you have any other '.gnucash' files in 
that folder/directory?


If so, can you provide a screenshot of Windows Explorer showing the list 
of files? (be sure to use the 'full details' view so we can see file 
creation and modification dates. You might need to 'turn on' one or both 
of those columns')


Regards,
Adrien

On 7/30/23 5:35 AM, Mahon Finbar via gnucash-user wrote:

Hello again,

After removing, renaming etc. the "offending file" as described, I now 
have a screen with 'unsaved book' which doesn't react to the 'close' 
option.


This appeared after a text box which said that the original offending 
file was not available, it was in the 'history' did I want to keep it, I 
said 'no' and then the screen I mentioned appeared.


I tried 'saving as' but it still won't go away.

Does anybody know what an 'unsaved book' is?

BTW, the same problem I have had all along (cannot save) is still there.


___
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.


[GNC] Cannot write to file a new wrinkle

2023-07-30 Thread Mahon Finbar via gnucash-user

Hello again,

After removing, renaming etc. the "offending file" as described, I now 
have a screen with 'unsaved book' which doesn't react to the 'close' option.


This appeared after a text box which said that the original offending 
file was not available, it was in the 'history' did I want to keep it, I 
said 'no' and then the screen I mentioned appeared.


I tried 'saving as' but it still won't go away.

Does anybody know what an 'unsaved book' is?

BTW, the same problem I have had all along (cannot save) is still there.

___
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.