INF: BCP and Formatting of MONEY Data Type

 Last reviewed: April 3, 1997
Article ID: Q96213

The information in this article applies to: 

  - Microsoft SQL Server version 4.2 for OS/2

SUMMARY

This article describes the implemented change of behavior of the Bulk Copy Program (BCP) in regards to formatting the MONEY data type when copied out in character mode (/c).

MORE INFORMATION

Starting with BCP version 4.2, MONEY data types when copied out of SQL Server in character mode are stored with commas separating the thousands, millions, billions, and so on. For example: 

   1,234,567.8900
This is a change of behavior from BCP version 1.1x, which does not insert the commas. For example; 

   1234567.8900
A design change request (number 7500) was entered against BCP version 4.2 asking that the behavior be changed so that no commas are inserted. Due to the large use of CSV (comma separated variable) data files, DCR 7500 was implemented in BCP version 4.2a.

Therefore, BCP version 4.2a now formats MONEY data types out in the same format that is seen under version 1.1x. For example: 

   1234567.8900

Additional query words: 4.20 4.20a bulk-copy dcr
Keywords : kbtool SSrvBCP
Version : 4.2
Platform : OS/2

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 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.