Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when you use an .odc file to connect to a specific table in a mail merge data source in a 2007 Office program or in Office 2003: "Record 'number' contained too few data fields"


View products that this article applies to.

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry

↑ Back to the top


Symptoms

Consider the following scenario. You use an .odc file to connect to a specific table in a mail merge data source. Then, you perform a mail merge in a 2007 Microsoft Office program or in a Microsoft Office 2003 program. In this scenario, the Mail Merge Recipients dialog box is empty.

You may receive the following error message in Microsoft Office Word 2003:
Record number contained too few data fields.
You may receive the following error message in Microsoft Office Publisher 2003:
Error has occurred: [Microsoft][ODBC SQL Server Driver][SQL Server] The cursor was not declared. [Microsoft][ODBC SQL Server Driver][SQL Server] Invalid object name.

↑ Back to the top


Cause

This problem may occur when the schema name is not included in the SQL statement that is sent to the ODBC data source.

↑ Back to the top


Resolution

This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest Office 2003 service pack, you do not have to install the hotfix.

Service pack information

This problem is corrected in Office 2003 Service Pack 3. To resolve this problem, obtain the latest service pack for Office 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
870924 How to obtain the latest service pack for Office 2003

After you install the service pack, follow the steps that are listed in the "How to enable the hotfix" section of the article to set the UseQualifiedTableNameForMailMerge registry key and to activate the hotfix.

Hotfix information

How to obtain the hotfix

This issue is fixed in the Office 2003 post-Service Pack 2 Hotfix Package that is dated April 12, 2006. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
917878 Description of the Office 2003 post-Service Pack 2 hotfix package: April 12, 2006

How to enable the hotfix

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To enable this hotfix, follow these steps:
  1. Exit all Office programs.
  2. Click Start, click Run, type regedit, and then click OK.
  3. If you are using a 2007 Office suite, locate and then click the following registry subkey:
    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common
    If you are using Office 2003, locate and then click the following registry subkey:
    HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common
  4. On the Edit menu, point to New, and then click DWORD Value.
  5. Type UseQualifiedTableNameForMailMerge, and then press ENTER.
  6. Right-click UseQualifiedTableNameForMailMerge, and then click Modify.
  7. In the Value data box, type 1, and then click OK.
  8. On the File menu, click Exit to exit Registry Editor.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This problem was first corrected in Office 2003 Service Pack 3.

↑ Back to the top


Keywords: kbnotautohotfix, kbregistry, kboffice2003sp3fix, kbmerge, kberrmsg, kbexpertiseinter, kbqfe, kbbug, kbfix, kbpubtypekc, kb

↑ Back to the top

Article Info
Article ID : 918295
Revision : 5
Created on : 4/17/2018
Published on : 4/18/2018
Exists online : False
Views : 226