BUG: "Word Has Detected a Field Name..." in Word 2.0

Last reviewed: June 27, 1995
Article ID: Q115288
The information in this article applies to:
  • Microsoft FoxPro for Windows, version 2.6

SYMPTOMS

If the Mail Merge Wizard is used to produce a mail merge in Microsoft Word version 2.0 for Windows, the following error message occurs when Word is invoked:

   Word has detected a field name in the header record which
   is not valid. This error must eventually be corrected in
   order to complete a successful Print Merge.

This error message is followed by a FoxPro error message:

   Cannot start Microsoft Word.

CAUSE

The data for the mail merge contains an extra comma after the last field. When Word reads this data, it assumes there should be another field, yet there is no corresponding field in the header record.

RESOLUTION

To resolve the problem, do one of the following:

  • Choose OK to accept the FoxPro error message. Choose the Fix Error Now button in the window produced by the Word error message. Add an extra header field to the list of header fields in Word.

    -or-

  • Use the SELECT command (or the Query Wizard) to produce a table that does not contain memo fields or general fields. Then use that table for the mail merge.

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.


Additional reference words: FoxWin 2.60 errmsg err msg buglist2.60
KBCategory: kbinterop kbtool kbprg kberrmsg kbbuglist
KBSubcategory: FxtoolWizother


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: June 27, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.