Microsoft KB Archive/942714

= FIX: Error message when you use the &quot;bcp_sendrow&quot; function in a SQL Server 2005-based application that uses a SQL Native Client provider: &quot;For BCP, all variable-length data must have either a length-prefix or a terminator specified&quot; =

Article ID: 942714

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Workgroup Edition
 * Microsoft SQL Server 2005 Express Edition
 * Microsoft SQL Server 2005 Express Edition with Advanced Services

-



Bug #: 50001822 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.



SYMPTOMS
Consider the following scenario:
 * You have a Microsoft SQL Server 2005-based application that uses a SQL Native Client provider to bulk copy data from program variables.
 * In the application, you use the bcp_bind function to bind data from program variables to a table column.
 * You set the cbIndicator argument for the bcp_bind function to 8.
 * You set the eDataType argument to SQLCHARACTER.
 * You use the bcp_sendrow function to send a row of data from program variables to SQL Server.

In this scenario, you receive the following error message:

[Microsoft][ODBC SQL Server Driver]For BCP, all variable-length data must have either a length-prefix or a terminator specified.

Additionally, if a NULL value is copied to a column in the target table, the column values of all the remaining records are incorrectly also set to NULL values.



RESOLUTION
The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

941450 Cumulative update package 4 for SQL Server 2005 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

941450 Cumulative update package 4 for SQL Server 2005 Service Pack 2

