R
Rick
Greetings!
Here's an odd one for you. When a few of my users try to
open a file in Word 2000 (SP3), the Open File dialog box
pops up, but then Word closes with no error message.
When they go back in to Word and try to open a file
again, it works fine for the rest of the day. The next
day, when they boot up again, the same thing happens
once, then all is well.
For the record, the users don't even get a chance to pick
a file from the Open File dialog box, it just flashes and
then kicks them to the desktop. Word itself opens fine,
it's not until you try to open a file in the network
folder that there's a problem.
Also, the default folder contains many subfolders (about
200-250), which also include one of more (but not more
than 3-4) levels of subfolders and probably a lot of
files.
Originally, the problem would only happen when they
browsed from their old defualt file location (let's call
that d:\, a mapped network drive) to the new default file
location (i.e., w:\, a different mapped network drive),
but I got it to stop on one PC by switching the default
file location (from d:\ to w:\). Not so on the other
workstations.
From this I suspect the problem lies in the folder (w:\),
but I'm not having much luck figuring out what's wrong.
This doesn't happen on the server when I browse the
folder locally and it only happens on some of the network
PCs (just about everyone on the network uses these
folders).
Any help would be appriciated.
Thanks.
Rick
Here's an odd one for you. When a few of my users try to
open a file in Word 2000 (SP3), the Open File dialog box
pops up, but then Word closes with no error message.
When they go back in to Word and try to open a file
again, it works fine for the rest of the day. The next
day, when they boot up again, the same thing happens
once, then all is well.
For the record, the users don't even get a chance to pick
a file from the Open File dialog box, it just flashes and
then kicks them to the desktop. Word itself opens fine,
it's not until you try to open a file in the network
folder that there's a problem.
Also, the default folder contains many subfolders (about
200-250), which also include one of more (but not more
than 3-4) levels of subfolders and probably a lot of
files.
Originally, the problem would only happen when they
browsed from their old defualt file location (let's call
that d:\, a mapped network drive) to the new default file
location (i.e., w:\, a different mapped network drive),
but I got it to stop on one PC by switching the default
file location (from d:\ to w:\). Not so on the other
workstations.
From this I suspect the problem lies in the folder (w:\),
but I'm not having much luck figuring out what's wrong.
This doesn't happen on the server when I browse the
folder locally and it only happens on some of the network
PCs (just about everyone on the network uses these
folders).
Any help would be appriciated.
Thanks.
Rick