PUB98: Publisher Fails to Recognize Delimiter After Merge
Article ID: 179213
Article Last Modified on 11/10/1999
APPLIES TO
- Microsoft Publisher 98 Standard Edition
This article was previously published under Q179213
SYMPTOMS
If you create a mail merge in Microsoft Publisher and then select a new
data source, which 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 originally create a mail merge with a
comma-delimited text file, Publisher will always uses a comma as the
delimiter for any new data source you attach to the mail merge. 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 (RAM), the driver does not 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
select a different data source by following these steps:
- On the Mail Merge menu, click Cancel Merge.
When you see the following message, click Yes:
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.
- On the Mail Merge menu, click Open Data Source.
- Click "Merge information from a file I already have."
- Select the new data source and click Open.
The delimiter for the new data source will be used.
STATUS
Microsoft is researching this problem and will post new information here
in the Microsoft Knowledge Base as it becomes available.
Additional query words: 98 pub98 mspub98 pub_98 5.00 publisher98 pub5 ms_pub98
Keywords: kbmerge kbprb KB179213