Word Sees Limited Memo Fields Using ODBC Drivers

Last reviewed: February 5, 1998
Article ID: Q122752
The information in this article applies to:
  • Microsoft Word for Windows, versions 6.0, 6.0a, 6.0c
  • Microsoft Word for Windows 95, versions 7.0, 7.0a

SYMPTOMS

When you perform a mail merge with a FoxPro or Microsoft Access database that contains many Memo fields, Word recognizes no more than two or three of those Memo fields. In addition, Word will drop any data from fields that appear after the second or third Memo field. If the first Memo field contains a large amount of data (200 paragraphs containing more than 80 characters each), Word will not recognize even the first field. Word may drop data from fields that appear after the first Memo field depending on the size of the first Memo field. This behavior occurs when you perform a mail merge using ODBC.

STATUS

Microsoft has confirmed this to be a problem in the 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.

WORKAROUNDS

Method 1: Change the Memo Fields to Text Fields. (NOTE: Text Fields have a

          255 character limit and may be truncated.)

Method 2 (with Access only): Use DDE instead of ODBC.


KBCategory: kbinterop buglist6.0 buglist6.0a buglist6.0c fixlist7.0
KBSubcategory: kbmerge
Additional reference words: 6.0 6.0a 6.0c FoxPro fox pro Access Insert
Database odbc memo field merge incomplete missing data header fields
word6 winword
Keywords : kbmerge
Version : 6.0 6.0a 6.0c 7.0 7.0a
Platform : WINDOWS


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