Oh I understood their purpose from your previous email (although it seems like an odd way to do CM - seems like that should be handled outside of the app). I was just not aware of their existence.
I have no idea why the backup process is capturing them, although they are not as hidden as one might suspect. I suspect I am doing something incorrectly. As for the reason you gave below, those are exceedingly uncommon on my end - so it is a mystery to me why so many were left behind. I know that OO would often crash when I would try to open it the first years I used it - but I long ago made the app open up at boot up. It only rarely crashes now, and never while I am editing the .ods files. So I do not know where they all came from. It’s just interesting to me - and a reminder to try the backup files once in a while. On Nov 3, 2018, at 3:28 PM, Keith N. McKenna <[email protected]<mailto:[email protected]>> wrote: On 11/2/2018 6:11 PM, chuck ef wrote: A reply to Keith McKenna. Found it. Things work fine. This was just an intellectual issue for me - the work around was trivial. I have never actually tested one of these backup files - I simply copied them to the drives. Installing the files onto this new machine was a first. Somehow, I don't understand it, but somehow those "lock" files came with the .ods files themselves. There were actually several in different backup folders. For other Mac users, the cmd + shift + "." keys make hidden files visible in Finder. You can also find them in a terminal window but this was easier. Thanks. <snip> Just to satisfy the intellectual curiosity the .lck files are not backup files. They are created every time a file is opened in AOO and are used Lock the file by being opened for write by someone else. The only reason one should be left behind is if AOO terminated abnormally. The most common reasons are because of a power surge or power failure or by closing the on a laptop before AOO has finished all it internal clean up. Glad we were able to solve your problem. Regards Keith
