FIX: BCP Format File Field Length Does Not Behave as Documented

Article translations Article translations
Article ID: 201857 - View products that this article applies to.
This article was previously published under Q201857
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 53018 (SQLBUG_70)
Expand all | Collapse all

Symptoms

Microsoft SQL Server Books Online states that if a length of zero (0) is specified in the format file for the data field, the zero length is ignored and that the length is read up to the termination character.

In actuality, Bcp.exe ignores the termination character, and depending on the length of zero (0) inserts a NULL value for that column.

Workaround

Specify a length for the field to be greater than the maximum data length of the real data in that column. Then, the separator is found first and the proper data inserted.

Status

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 201857 - Last Review: November 1, 2013 - Revision: 3.0
Applies to
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB201857

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com