M
mrlegowatch
Hi,
I work in an office environment which consists primarily of PCs using
Office (Word, Excel, etc.). I have found that when I save an existing
Word or Excel file (Office 2004 with all the updates) which is on a
network drive with multiple user and group permissions, the write
permission reverts to just me, instead of the multiple users and
groups, i.e., it becomes read-only for everyone else. It doesn't
matter if the file is open with "(shared)" access on Windows first, if
I save it, it becomes read-only to everyone else.
Currently, I have to remember to immediately drop into Terminal and
type 'chmod ug+w file-name' before anyone else notices that I'm using
Office:Mac. Unfortunately, I've slipped up a couple of times, and
people are starting to notice (and stare, and become annoyed). Am I
doing something wrong with saving, is my IT department doing something
wrong with the server (or users and groups), or is there a bug in the
Office:Mac save command which strips write permissions on save?
I work in an office environment which consists primarily of PCs using
Office (Word, Excel, etc.). I have found that when I save an existing
Word or Excel file (Office 2004 with all the updates) which is on a
network drive with multiple user and group permissions, the write
permission reverts to just me, instead of the multiple users and
groups, i.e., it becomes read-only for everyone else. It doesn't
matter if the file is open with "(shared)" access on Windows first, if
I save it, it becomes read-only to everyone else.
Currently, I have to remember to immediately drop into Terminal and
type 'chmod ug+w file-name' before anyone else notices that I'm using
Office:Mac. Unfortunately, I've slipped up a couple of times, and
people are starting to notice (and stare, and become annoyed). Am I
doing something wrong with saving, is my IT department doing something
wrong with the server (or users and groups), or is there a bug in the
Office:Mac save command which strips write permissions on save?