I've never tried renaming the document after it being recovered. I just
know it recovers as a Read-Only file. That has been an inconvenience but
not an important issue because I could simply do a Save-As to a new file
name in the same folder and that new file would be both Read and Write
again.
Thank you, I will look into that. I appreciate the tip.
Robert
On Mon, Aug 5, 2013 at 5:39 PM, John Hart wrote:
> On 8/5/2013 2:38 PM, Duffield wrote:
>
>> Unfortunately, the blue screens took care of the rebooting question-there
>> have been innumerable reboots since this problem appeared
On 6/08/2013 7:38 AM, Duffield wrote:
Unfortunately, the blue screens took care of the rebooting question-there
have been innumerable reboots since this problem appeared.
I know that when a reboot has been forced while an OO file is open, during
the boot up process OO gives the option to recove
On 8/5/2013 2:38 PM, Duffield wrote:
Unfortunately, the blue screens took care of the rebooting question-there
have been innumerable reboots since this problem appeared.
I know that when a reboot has been forced while an OO file is open, during
the boot up process OO gives the option to recover
Unfortunately, the blue screens took care of the rebooting question-there
have been innumerable reboots since this problem appeared.
I know that when a reboot has been forced while an OO file is open, during
the boot up process OO gives the option to recover the file (but from that
point on it is
Check the temporary folder of the system (see in OO menu
Tools>Options>OO>Paths). If there are folders like sgmlf.tmp with a file having
the same name inside, make a copy of that file, rename it in .ods and cross your
fingers. If you have not rebooted, you might have those files still there.
N
