Hello again,
Ok, I've got DAV working on my server and I still notice an odd
difference in behavior between Writer 1.1.4 and 1.9.100. With 1.1.4
both encoded ASCII text files and .sxw files are opened read/write;
1.9.100 opens encoded ASCII text files read/write but .sxw files as
readonly.
Hello once again,
Alright, looks like there was some kind of negative interaction between
1.9.100 and the previous version that existed on my computer. I removed
that version and the current one, then reinstalled 1.9.100 and
everything seems to work fine.
thanks for your time,
Matthew
Hello
Mathias Bauer wrote:
That lets me think that our ftp content provider supports a readonly
property for its content, maybe the server of Matthew tells that the
files are readonly and yours doesn't? But I have to check this.
There is some support for a readonly attribute in the ftp content
Mathias Bauer wrote:
BTW; did you consider using WebDAV instead of ftp? It's much more
reliable especially in this regards and maybe in future OOo will support
more advanced features of this protocol.
Much thanks for the suggestion. No I hadn't considered it, but now that
you've mentioned
Matthew L. Avizinis wrote:
Mathias Bauer wrote:
BTW; did you consider using WebDAV instead of ftp? It's much more
reliable especially in this regards and maybe in future OOo will support
more advanced features of this protocol.
Much thanks for the suggestion. No I hadn't considered it,
Mathias Bauer pe v t 10. 05. 2005 v 19:04 +0200:
You should be more clear: do they get opened readonly *always*?
If yes: it could be a problem in OOo.
If no (means: only sometimes): I'm a little bit clueless.
I was writing similiar macro in the Basic (m97, m100, ...) and have no
problems at
Additionally, I've noticed that if I open the ftp file directly by
typing it in the URL box (in 1.1.4) the document will open read/write,
but with 1.9.100 it opens readonly, which says to me that either some
program setting is different (and I haven't found one which controls
this, like a
