A
AK_Techie
Re: Updating Cross Reference Fields in Word Professional 2003 SP2
In previous versions of Word, we used to be able to place our cursor
anywhere on a cross reference in normal view and press [F9] (also confirmed
that it works this way using Word XP with all service packs installed).
However, using Word 2003 SP2, we receive the error message "Run-time error
'5184': Command only available in print layout view.
Switching to print layout view and with the cursor still anywhere on the
reference, when we press [F9], we receive the error message "Run-time error
'5101': This bookmark does not exist.
The only way that the reference will update is if (1) we are in Print Layout
View, and (2) the reference is highlighted before pressing [F9] (vs. in
normal view and/or the cursor anywhere on the reference code).
I uninstalled the Microsoft Office 2003 on one workstation and reinstalled
from stratch. Even with no service packs installed, Word 2003 produces the
errors referenced above. Are our program disk defective? Or, does everyone
receive the errors described above? I would appreciate any feedback received.
In previous versions of Word, we used to be able to place our cursor
anywhere on a cross reference in normal view and press [F9] (also confirmed
that it works this way using Word XP with all service packs installed).
However, using Word 2003 SP2, we receive the error message "Run-time error
'5184': Command only available in print layout view.
Switching to print layout view and with the cursor still anywhere on the
reference, when we press [F9], we receive the error message "Run-time error
'5101': This bookmark does not exist.
The only way that the reference will update is if (1) we are in Print Layout
View, and (2) the reference is highlighted before pressing [F9] (vs. in
normal view and/or the cursor anywhere on the reference code).
I uninstalled the Microsoft Office 2003 on one workstation and reinstalled
from stratch. Even with no service packs installed, Word 2003 produces the
errors referenced above. Are our program disk defective? Or, does everyone
receive the errors described above? I would appreciate any feedback received.