 |
 |
 |
 |
 |
||||||||||||||||
 |
 |
 |
|
|||||||||||||||||
 |
|
|||||||||||||||||||
 |
|
|||||||||||||||||||
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
||||
 |
 |
 |
 |
 |
|
|||||||||||||||
 |
 |
 |
|
|||||||||||||||||
 |
|
|||||||||||||||||||
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Document information
Using CommaBefore displaying any numeric data on screen WinSQL asks the ODBC driver to convert it into a character value. It is important to know that this conversion is done by the ODBC driver and therefore, there is no setting in WinSQL that can affect this format. You will see a comma as a decimal separator if the locale on your machine is set to a country that uses a comma to separate the decimal part of a number. IBM's CLI library offers a way to change this behaviour. To
force the ODBC driver to use a period instead of a comma, edit the
db2cli.ini, which by default is located in C:\Program Files\IBM\SQLLIB.
Add the following line in the section pertaining to your database.
Patch2=15 Refer the following links to get more information about CLI parameters.
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.apdv.cli.doc/doc/r0008805.htm
Add a comment to this documentDo you have a helpful tip related to this document that you'd like to share with other users? Please add it below. Your name and tip will appear at the end of the document text. | ||||||||||||||||||
