BUG: Money Values Incorrectly Use Thousand SeparatorLast reviewed: April 30, 1997Article ID: Q118884 |
The information in this article applies to:
- Microsoft SQL Server Programmer's Toolkit, version 4.2BUG# 10091 (4.2)
SYMPTOMSUnder Microsoft Windows NT if the thousand separator is set to null or a space, then the dbconvert function will generate a " instead of a space or a null whenever converting a money value to a string. NOTE: The 1000 separator is set using the International Applet in the NT Control Panel. For example,
SELECT $1234567.80will display as
1"234"567.80Under MS-DOS or OS/2, setting the thousand separator to a null by changing the corresponding entry in SQLCOMMN.LOC to '' or leaving it blank will cause the separator to be replaced by a carry return. For example,
SELECT $1234567.80will display as
1 234 567.80 CAUSESpecifying a blank or null separator through Control Panel causes Windows NT to respectively store "" and " " in the registry. DB-Library, in turn, only considers the first character. Under MS-DOS and OS/2, DB-Library incorrectly handles a blank or null thousand separator.
WORKAROUNDFor Windows NT, changing the registry entry \current user\control panel\international\sthousand to space works as expected. Setting it to null causes the separator to default to a comma. Under MS-DOS and OS/2, do not use a null separator.
STATUSMicrosoft has confirmed this to be a problem in DB-Library version 4.20.50. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words: dblib
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |