I had a problem
>>
>>> ... the changes file (with write-access)
>>> can not be opened: more precisely, the primitive (in StandardFileStream)
>>> primOpen: fileName writable: true returns nil, while the file definitely
>>does
>>> exist. I vaguely remember a thread about this behavior. Is this a bug
>>with a
>>> workaround, or am I doing something wrong?
>>

and Reinier replied:

>>check the following:
>>
>>1. are you allowed to write on this network disk (I experienced this with
>>VSE)

I was sure I had write-access, but I am not so sure anymore I really had!! I
will first check this, before bothering you again! Thanks

>>2. is the changes file perhaps marked as read-only (I had to fix this for
>>the FileList as well)
>>3. are more than one users trying to open the same file for writing (can
>>only be one)
>>4. is the file name allowed on that network disk (improbable because you
>>opened the other ones)
>>5. last: can you open it read-only
>>
>>Reinier.