If you do a search for all files with file extension ".lck" what
reason do you have to suppose that it is a lock file for a gnucach
file? I will repeat, this is a rather common method for preventing
simultaneous access to a resource. Do you KNOW that none of your
other applications are using the lock file method?
Michael, that is a fair point as I noted in a previous reply, but the
OP just reported, as you quoted, that the LCK file in question *was*
for a GnuCash file *because* it had a GnuCash file name in it. Did you
not read that part?
"GNU FEB 12 2019.gnucash.20210219151108.gnucash.LCK"
And while that is a file from gnucash it is almost certainly NOT the
name the user assigned to the file that is their books << and yes, it is
a gnucash internal backup file >> The presence of that lock means that
this backup file was left open. So while OK to delete the lock (if you
know that gnucash is not running) it is NOTÂ the file you want to open
when you start gnucash. Note that if one did accidentally open this file
could be on the "recently open" list and if on the top if the list, will
be reopened when you start gnucash. THIS IS NOT WHAT YOU WANT.
So LOOK at what gets opened when you start gnucash (the bar should show
the file name). If NOT the right file, use file=>open to specify the
correct file name and then once open, shut down. Now wen you reopen
gnucash will be on top of the list (most recently opened)
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.
