PUB2000: Publisher Fails to Recognize Delimiter After Merge (212611)
The information in this article applies to:
This article was previously published under Q212611 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. To do this, following these steps:
- On the Mail Merge menu, click Cancel Merge.
When you receive 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 another type of file.
- Select the new data source and click Open.
The delimiter for the new data source will be used.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Publisher.
| Modification Type: | Major | Last Reviewed: | 6/29/1999 |
|---|
| Keywords: | kbmerge kbprb KB212611 |
|---|
|