Mac Forum / Applications / Word / March 2006

Hi Phil:

Regrettably, Rob's "cure" is not possible for you because your back end is a
Windows server.

Your problem "is" a result of the remote home folder.  Effectively, the
user's Mac ends up with "two" paths to the same resource.  When it attempts
to Save a file through one path, it encounters a server edit lock on the
resource reported via the second path.  This makes it appear that the file
is in use to a different user.

Until Apple gets their bug fixed, the only simple solution is to tell your
Mac users to work on their local drive and use Finder to copy the result
back to the server.

Not ideal:  it leads to the possibility that another user could change the
file that the user is working on.  To prevent this, The user could open the
file on the server and Save As to their local drive.  They could then go
back to the server and OPEN the file again.  Leave that open document in the
background to maintain an edit lock on the server, but work on the copy they
have on their local drive.

When they have finished, close the window holding the file open on the
server.  They may ("should") then be able to Save As back to the server and
overwrite the file they just released.

Good luck explaining this to unsophisticated users :-)

The bad news is that I don't think Apple is *going* to fix their bug,
certainly not any time before OS 10.5.  There's a good chance that the next
version of Microsoft Office will not trigger the problem.  There's a small
possibility that an Intel Mac won't display the problem (but don't get your
hopes up: I think they're too closely similar).  As far as I know, OS 10.3.9
doesn't display the problem.

Not good...

Cheers

On 31/3/06 1:43 AM, in article
1143733415.303133.257230@e56g2000cwe.googlegroups.com, "CyberTaz"
<generaltaz1@comcast.net> wrote: