Read ONLY when open network files

[Nelson Leung]

Case 1
1. User A open a network file call A.xls
2. After updated, user A close the file BUT NOT Excel.
3. User B try to open that updated file A.xls
4. User B got the message READ ONLY.

Case 2
1. User A open a network file call A.xls
2. After updated, user A close the file AND the Excel.
3. User B try to open that updated file A.xls
4. User B can normally open that file.

Server: Windows 2000 Server with SP4
Workstation: Windows 2000 Pro with SP4
Office: Office Professional 2000 with SP3
Users Access Rights: READ & WRITE

Any suggestion?

Many Thanks.
Nelson

 

[Keme]

Case 1
1. User A open a network file call A.xls
2. After updated, user A close the file BUT NOT Excel.
3. User B try to open that updated file A.xls
4. User B got the message READ ONLY.

Case 2
1. User A open a network file call A.xls
2. After updated, user A close the file AND the Excel.
3. User B try to open that updated file A.xls
4. User B can normally open that file.

Server: Windows 2000 Server with SP4
Workstation: Windows 2000 Pro with SP4
Office: Office Professional 2000 with SP3
Users Access Rights: READ & WRITE

Any suggestion?

Many Thanks.
Nelson

The problem seems to be caused by some kind of locking mechanism. MS
Office uses a "lockfile" to communicate file usage to other instances of
Office applications. Windows servers use file locking for the same
purpose. Still, I don't see any possible conflict in that.

The users may need "modify" rights to correctly alter the corresponding
lockfile when closing an MS Office file, or there may be a timeout on
network file closing on the server, causing similar results. Directory
caching on the workstation could also be the culprit.