D
Dave Woolcock
We are now on Word2003 but our old documents may have been created under
previous versions. Most were created from templates on a (Netware) server,
stored in g:\wp\templates. Unfortunately Word doesn't store the mapped
drive letter (g
but translates it as \\servername underneath.
We are now in the middle of a server change-over from Netware to Windows
servers, with a new naming regime. Retiring the old servers now causes
problems - some severe - when opening a document invisibly linked to a
retired server. On most machines it can mean a delay of 15 to 45 seconds
(pretty unaccaptable). Yet some machines are still egg-timing 10 minutes
later. Either way - users complain that Word is broken.
We have tried:
Waiting for the doc to open then blanking out the template link by hand and
resaving - this works but needs R/W access, changes the doc write-date, and
we have a million documents mainly read-only. The write-date is valuable
information to us.
spoofing DNS to point the old server name to a new server... not very
successful.
spoofing the HOSTS file to do the same.
Running a macro to change the link to "normal" - useless as it has to wait
for the doc to load before it triggers the macro.
Running the free Word2003 reader (why would it need to open a template?) -
it does anyway and makes no difference.
Searching the internet - I think a MS technote suggests not changing the
servername or manually resaving all the documents.
Opening a Word doc in Open Office - jeez - that works (but we have just
spent shedloads of money on MS licences !!!)
Does anyone have a better solution?
previous versions. Most were created from templates on a (Netware) server,
stored in g:\wp\templates. Unfortunately Word doesn't store the mapped
drive letter (g
but translates it as \\servername underneath.We are now in the middle of a server change-over from Netware to Windows
servers, with a new naming regime. Retiring the old servers now causes
problems - some severe - when opening a document invisibly linked to a
retired server. On most machines it can mean a delay of 15 to 45 seconds
(pretty unaccaptable). Yet some machines are still egg-timing 10 minutes
later. Either way - users complain that Word is broken.
We have tried:
Waiting for the doc to open then blanking out the template link by hand and
resaving - this works but needs R/W access, changes the doc write-date, and
we have a million documents mainly read-only. The write-date is valuable
information to us.
spoofing DNS to point the old server name to a new server... not very
successful.
spoofing the HOSTS file to do the same.
Running a macro to change the link to "normal" - useless as it has to wait
for the doc to load before it triggers the macro.
Running the free Word2003 reader (why would it need to open a template?) -
it does anyway and makes no difference.
Searching the internet - I think a MS technote suggests not changing the
servername or manually resaving all the documents.
Opening a Word doc in Open Office - jeez - that works (but we have just
spent shedloads of money on MS licences !!!)
Does anyone have a better solution?