H
Hall
A network folder's security permissions specifies "read & execute", "list
folder contents", and "read" for everyone, and my ID, as folder owner has
all permissions.
Files in this folder similarly have full permissions for me, and read-only
for everyone else.
If someone else opens an Excel file in this folder, it opens up in read-only
mode, and while he has it open, I can still overwrite it, delete it, or
rename it.
But if someone else opens a PDF or MS Project file in this folder, I am
unable to overwrite, rename, or delete it. The server software, for these
file types, is maintaining a lock on the file, and I can't do a thing unless
the server admin removes the lock or the other user closes the application
with the file.
Why the difference based on the file type?
Can we change anything at the server admin level so that no one can hold a
lock on any file if access is just read-only?
We're on 2003 enterprise server, with nt4 domain.
Thx
folder contents", and "read" for everyone, and my ID, as folder owner has
all permissions.
Files in this folder similarly have full permissions for me, and read-only
for everyone else.
If someone else opens an Excel file in this folder, it opens up in read-only
mode, and while he has it open, I can still overwrite it, delete it, or
rename it.
But if someone else opens a PDF or MS Project file in this folder, I am
unable to overwrite, rename, or delete it. The server software, for these
file types, is maintaining a lock on the file, and I can't do a thing unless
the server admin removes the lock or the other user closes the application
with the file.
Why the difference based on the file type?
Can we change anything at the server admin level so that no one can hold a
lock on any file if access is just read-only?
We're on 2003 enterprise server, with nt4 domain.
Thx