the sequence of having soffice lockup/kill/recovery seems to create a
number of errors that are difficult to work around.
if soffice hangs, i kill it.
soffice then recovers the file.
i try to write the file which generates a 'general file IO' error.
i write to a new file name. which i can then read/write/modify without
issue.
if i copy the new file to the original file name, via the command line,
then open the original file, it opens in read only mode.
i have searched for lock files and can find none.
has anyone else seen this? does anyone know of a solution?
thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
