BUG: BCP format file created for quote enclosed data cannot be

Last reviewed: April 8, 1997
Article ID: Q153131
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5

SYMPTOMS

A format file created by SQL server to generate quote-enclosed data cannot be reused for transferring data out.

If you use BCP OUT to transfer data into an output file in the form:

   field1,"field2","field3","field4"

after the format file is created interactively, the data is successfully written out to the output file specified. However, every subsequent attempt at using the format file created earlier for transferring data (using BCP OUT) from the same table will format data in a different way, causing the output file to be different.

WORKAROUND

Do not use the format file more than once if the data being transferred with BCP OUT is for purposes other than use with SQL server.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information herein the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The format file can however be used to transfer data from the output file into the table, using BCP. But if BCP OUT of data was for puposes other than populating a SQL server table this may cause a problem. Each time the data needs to be written out using BCP, a new format file needs to be created interactively or manually.


Additional query words: kbbug656
Keywords : kbbug6.00
Version : 6.0 6.5
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.