WD97: Invalid Page Fault Using DocVariable Field

Last reviewed: July 31, 1997
Article ID: Q168923
The information in this article applies to:
  • Microsoft Word 97 for Windows

SYMPTOMS

When you use the DocVariable field in a header, footer, or text box, the following error may occur:

   This program has performed an illegal operation and will be shut
   down. If the problem persists, contact the program vendor.

If you click Details, you will receive the following error message:

   WINWORD caused an invalid page fault in module WINWORD.EXE at
   0137:3037f1db.

WORKAROUND

To work around this problem, use custom document properties (on the File menu, click Properties, and then click the Custom tab) to set custom document variables and then use the DocProperty field to use the values in a header, footer, or text box.

To Create a Custom Document Property

  1. On the File menu, click Properties, and then click the Custom tab.

  2. In the Name box, type a name for the custom property, or select a name from the list.

  3. In the Type box, click the type of property you want.

  4. In the Value box, type a value for the property.

    The value you enter must match the selection in the Type box. For example, if you click Number in the Type box, you must type a number in the Value box. Values that don't match the property type are stored as text.

  5. Click Add.

  6. Click OK.

To Insert the DocProperty Field in the Document

  1. Click where you want to insert the DocProperty field.

  2. On the Insert menu, click Field.

  3. Click the Document Information category, and then click the DocProperty field.

  4. To add the Custom Document Property to the field, click Options.

  5. From the Property list, select the custom Property.

  6. Click Add To Field.

  7. In the Field Options dialog box, click OK.

  8. In the Fields dialog box, click OK.

NOTE: For more information about a specific field or option, while in the Field dialog box, select the field name or option, and then press F1.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

If you insert a blank DocVariable field into a header or footer, that is, when you insert the field with no reference to a stored document variable, and then you later add the document variable reference and update the field, you do not receive the error described in the "Symptoms" section of this article. However, when you update the DocVariable field, the field remains blank.

Performing these same steps in a text box causes the error described in the "Symptoms" section of this article to occur when you update the field.

REFERENCES

For more information about the DocVariable field, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q166098
   TITLE     : WD97: DocVariable Field Is Autoindex Field After Conversion

For more information about "the DocVariable field," click the Office Assistant, type "docvariable," click Search, and then click "Field Codes:DocVariable field."

NOTE: If the Assistant is hidden, click the Office Assistant button on the Standard toolbar. If Word Help is not installed on your computer, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q120802
   TITLE     : Office: How to Add/Remove a Single Office
               Program or Component


Additional query words: 8.0 8.0
Keywords : kbfield word8 word97 kberrmsg
Version : 97
Platform : WINDOWS
Issue type : kbbug


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 31, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.