Article ID: 218688
Article Last Modified on 6/29/1999
APPLIES TO
- Microsoft Publisher 2000 Standard Edition
This article was previously published under Q218688
SYMPTOMS
If you try to use a Microsoft FoxPro or a Borland DBase (.dbf) file that has a long file name as the data source for a mail merge in Microsoft Publisher, you may receive the following error message:
If you click Yes, Publisher gives the following error message:
NOTE: If you click Yes, Microsoft Publisher attempts to reinstall the Mail Merge feature and after the setup is complete, you receive the same error message.
CAUSE
When you attempt to use a Borland DBase file in a Mail Merge publication, Microsoft JET looks for the Borland database engine to utilize it. If it is not found, JET uses its own ISAM's (Index Sequential Access Method).
The Microsoft FoxPro and Borland DBase ISAM's provided by Microsoft JET do not support long file names. These ISAM's only support files using the 8.3 naming convention.
NOTE: The Borland database engine that ships with many Borland products designed for Windows 95/98/NT does support long file names. This engine will also open a FoxPro file as well.
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
WORKAROUND
To locate the dbase file used for the data source and rename the filename to comply with the 8.3 naming convention, follow these steps:
- On the Windows Start menu, point to Find, and click Files or Folders.
- In the Named box, type:*.dbf.
- In the Look In box, click Local hard drives.
- Click to select the Include Subfolders check box.
- Click Find Now.
- Right-click on the file you are using as your data source and click Rename.
- Change the filename to 8 characters or less, not including the 3 character extension.
For Example: If your filename is MyLongFileName.dbf, you will want to rename the file to something like MyFile.dbf.
- Run the mail merge again using the renamed database file as your data source.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Publisher 2000.
Additional query words: PUB2K PUB2000 PUB 2000 PUB9 9.0
Keywords: kbbug kbmerge kbpending KB218688