Article ID: 813815 - Last Review: April 7, 2006 - Revision: 4.2 WD2002: Conditional Field That References AutoText Entries Does Not Completely Update the First Time
On This PageSYMPTOMSWhen you update a conditional field that is contained in a
document that was created in an earlier version of Word (for example, Word
2000), and the conditional field references AutoText entries, the new results
of the update may not display the complete contents of the AutoText fields. If
you update the conditional field a second time, the complete contents are now
displayed correctly. For example, if you open a Word document that contains a conditional field similar to the following, the field results display the results of the previous update: { IF "Y" = "N" "True" "{ AUTOTEXT NAMEI() }, { AUTOTEXT ADDRESS() }" } When you select the conditional field and then press
F9, the field is partially updated. If you press F9 a second time with the
conditional field selected, the complete results of the field update now
appear.Note If the field code of the conditional field appears instead of the results of the field, press ALT+F9 to switch to the results of the field. RESOLUTIONService Pack InformationThis problem is corrected in Office XP Service Pack 3.To resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:307841
(http://support.microsoft.com/kb/307841/
)
How to obtain the latest Office XP Service Pack Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this fix should have the following file attributes or later: Date Time Size File name ---------------------------------------------------------- 28-Feb-2003 14:24 3,005,024 Winwordop.msp (Client) 28-Feb-2003 15:55 8,296,120 Winwordff.msp (Full file) After the hotfix is installed, the English version of this fix will have the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name --------------------------------------------------------------- 08-Jan-2003 10:55:46 10.0.4721.0 10,182,656 Winword.exe 325671
(http://support.microsoft.com/kb/325671/EN-US/
)
OFFXP: Overview of the Office XP Service Pack 2 Additionally, you may have to install Windows Installer 2.0 to
install this fix. For additional information about the Windows Installer
requirement for post-Office XP SP-2 fixes, click the following article number
to see the article in the Microsoft Knowledge Base: 330537
(http://support.microsoft.com/kb/330537/EN-US/
)
OFFXP: Office XP Updates and Patches Released After September 2002 May Require Windows Installer 2.0 STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Office XP Service Pack 3.
| Article Translations
|
Back to the top
