I have a domain with 4 sites with a folder sitting in a share on one windows
2003 server in one of the sites. This folder contains word documents that
can be opened by anyone if they use File-open command inside of Word.
(2003). Users from 2 of the sites can double click the file to open it,
however the users from the other two sites can not open by doubleclicking the
file. They only are able to open from inside Word. When the file fails to
open, the application Word seems to freeze for a while and no errors are
generated. It doesn't appear to be a permissions issue as I have given one
of the test users full control in the directory with the problem remaining.
Also, a user from a working site can sit down at a workstation at the
non-working site and open the files fine using their account. The user
accounts from the non working sites fail when logged on to workstations from
the functioning sites.

What the heck is causing this?

Thanks in advance
Marc

UPDATE: I was able to rename the folder from "Draft Directives" to just
Draft and it works. Is there some reason or limit on name size in Word when
using Explorer to open files? The shortest document would have a path of
about 50 characters.

"Marc" wrote:

I have a domain with 4 sites with a folder sitting in a share on one windows
2003 server in one of the sites. This folder contains word documents that
can be opened by anyone if they use File-open command inside of Word.
(2003). Users from 2 of the sites can double click the file to open it,
however the users from the other two sites can not open by doubleclicking the
file. They only are able to open from inside Word. When the file fails to
open, the application Word seems to freeze for a while and no errors are
generated. It doesn't appear to be a permissions issue as I have given one
of the test users full control in the directory with the problem remaining.
Also, a user from a working site can sit down at a workstation at the
non-working site and open the files fine using their account. The user
accounts from the non working sites fail when logged on to workstations from
the functioning sites.

What the heck is causing this?

Thanks in advance
Marc