Applying XP SP2 causes error in Word when navigating via hyperlink
From: gardoglee (gardoglee_at_discussions.microsoft.com)
Date: 01/28/05
- Next message: Ben Wylie: "The Printer has not responded, but..."
- Previous message: pete via OfficeKB.com: "text contracts into a single space on Word 2003"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 28 Jan 2005 08:57:03 -0800
We have a number of Word XP Pro documents which we have been publishing to
network drives, IIS web servers and Apache web servers. We have been able to
use relative hyperlinks within these documents for navigation on all three
access platforms for some time. Our users have Windows XP Pro with Office XP
Pro.
We use many hyperlinks within the documents which point to specific phrases
within a document. As an example, a hyperlink from an overview document to a
background document might be defined in the <cntl-k> dialog box as
"../Background_Documents/Configuration/Hardware.doc#Network diagram" This is
to direct the browser or application to open the document (Hardware.doc) and
perform a 'Find' on the string "Network diagram".
This has worked for us in all cases until the application of XP Service Pack
2. After SP2 is applied, the hyperlink routine works correctly if the
documents are being accessed on a file server, but does not execute correctly
when the documents are accessed through a web server. The correct target
document is opened, but the positioning within the document fails. When the
<cntl-f> dialog is opened, it appears that the find string which ahs been
passed to the new document session has the '#' character still in the find
string. In the above example, this would then mean that the find routine is
looking for "#Network diagram". Since this string is not found in the target
document, the newly opened document is left positioned at the top, rather
than at the correct position.
We have demonstrated that this is a result of the XP SP2 application by
opening documets with a machine on which SP2 has not yet been applied (works
correctly), opening with a machine on which SP2 has been applied (fails), and
by opening on a machine on whihc we have installed and then uninstalled SP2
(works correctly again after uninstall). This has been repeated from
multiple sites, across multiple configurations, etc. We are confident that
the problem is a direct result of XP SP2.
Has anyone else experienced this problem, or have any ideas on how to
remediate?
- Next message: Ben Wylie: "The Printer has not responded, but..."
- Previous message: pete via OfficeKB.com: "text contracts into a single space on Word 2003"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
