Slow Opening Microsoft Word Documents

[Paul Moloney]

A co-worker who accesses a HTTP server of our documentation has
commented that it takes up to a minute for these documents to load.
The documents are based
on a standard template on a server that he appears not to have access
to.

In this instance, I would have thought that Word, once it finds the
template
is not accessible, would simply load the document. Otherwise,
templates are totally impractical since anyone who doesn't have access
to the same server as the template will have the same hanging problem.

Does anyone know why Word might be hanging and how I can fix this?
Adding and removing references to the template from each doc as I
start/finish editing it is impractical.

Thanks,

P.

 

[TF]

Paul

The problem is that if the 'opener' has a network connection, Windows will
go out and check all network paths before giving up on find the template.
The short answer is that once the user has opened the document, if he/she
uses Tools, Templates & Addins, delete the attached template. Then it will
open quickly thereafter.



:A co-worker who accesses a HTTP server of our documentation has
: commented that it takes up to a minute for these documents to load.
: The documents are based
: on a standard template on a server that he appears not to have access
: to.
:
: In this instance, I would have thought that Word, once it finds the
: template
: is not accessible, would simply load the document. Otherwise,
: templates are totally impractical since anyone who doesn't have access
: to the same server as the template will have the same hanging problem.
:
: Does anyone know why Word might be hanging and how I can fix this?
: Adding and removing references to the template from each doc as I
: start/finish editing it is impractical.
:
: Thanks,
:
: P.

 

[Paul Moloney]

Paul

The problem is that if the 'opener' has a network connection, Windows will
go out and check all network paths before giving up on find the template.
The short answer is that once the user has opened the document, if he/she
uses Tools, Templates & Addins, delete the attached template. Then it will
open quickly thereafter.

Hi Terry,

The problem is that in our company, only writers have write access to
documentation, so the user would be able to remove the template
from the doc, but not save this change. The other problem is that I don't
want them doing this in the first place! At the last count, we were
maintaining
6,000 Word documents, and I don't want other people deleting template
references from these documents.

Do you know of any other remedy to this? And is the problem only limited to
users who have a network connection, but not a connection to the machine
hosting the template?

P.

 

[TF]

Load all the templates on their local HDD.

Terry

:
: "TF" <terryfarrell%40%6d%73%6e%2ecom> wrote in message
: : > Paul
:
: > The problem is that if the 'opener' has a network connection, Windows
will
: > go out and check all network paths before giving up on find the
template.
: > The short answer is that once the user has opened the document, if
he/she
: > uses Tools, Templates & Addins, delete the attached template. Then it
will
: > open quickly thereafter.
:
: Hi Terry,
:
: The problem is that in our company, only writers have write access to
: documentation, so the user would be able to remove the template
: from the doc, but not save this change. The other problem is that I don't
: want them doing this in the first place! At the last count, we were
: maintaining
: 6,000 Word documents, and I don't want other people deleting template
: references from these documents.
:
: Do you know of any other remedy to this? And is the problem only limited
to
: users who have a network connection, but not a connection to the machine
: hosting the template?
:
: P.
:
:
:

 

[John C]

Paul,

Forgive my jumping into the middle of this without having seen how it
started out but...

I had a network where file opening performance for Word Docs (Word 97) was
dismal (tiny 100Mbps LAN, v little traffic, up to 8 minutes to open a single
doc on the server and just as long when the document was on a local hard
disk).

By dragging one of the docs into Notepad, I was able to see that the
document contained references to servers that had long since been removed
from the network. By setting up WINS to provide static references
associating the IP address of the current server with the names of the old
(removed) servers, the "problem" was eliminated (I quote "problem" because
we'd really only dealt with a symptom rather than a problem). I thought
this was really clever and then I found a reference to this MSKB article in
this NG http://support.microsoft.com/?kbid=830561. I think that this
article might apply to other versions of Word (although some of the VB might
have to be tweaked)... your call.

Point to note about the WINS piece... This was a server migration, I had the
same directory and share structure across the generations of server...

Regards
JC