Microsoft KB Archive/173209

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 10:06, 21 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Article ID: 173209

Article Last Modified on 11/7/2002



APPLIES TO

  • Microsoft Publisher 97 Standard Edition



This article was previously published under Q173209

SYMPTOMS

If you create a mail merge in Microsoft Publisher and change to a new data source, and that new data source uses a different field delimiter, Publisher does not recognize the delimiter for the new data source and uses the original delimiter. For example, if you create a mail merge with a comma-delimited text file, Publisher always uses a comma as the delimiter for any new data source. This is true even if you explicitly specify another kind of delimiter.

CAUSE

If the indexed sequential access method (ISAM) driver is already loaded in random access memory, the driver does update the field delimiter definition when you connect to a new data source.

WORKAROUND

To workaround this problem, cancel the original mail merge before you change to a different data source. To do this, follow these steps:

  1. On the Mail Merge menu, click Cancel Merge.

    You then see a dialog box with the following message:

    Are you sure you want to cancel this merge?

    Click Yes to clear all merge information permanently and convert all merge fields to plain text. Click No to retain all merge information.

  2. Click Yes to clear merge information.
  3. On the Mail Merge menu, click Open Data Source.
  4. Click "Merge information from a file I already have."
  5. Locate the new data source, select it, and then click Open.

The delimiter for the new data source is used.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION


Additional query words: iisam pub97 unable records messed up 4.00 mm mailmerge mail-merge

Keywords: kbmerge kbprb kbusage KB173209