Feedback
Did this article resolve your question/issue?

   

Article

The precision of float data is incorrect with Connect for ODBC for SQLServer driver.

Information

 
TitleThe precision of float data is incorrect with Connect for ODBC for SQLServer driver.
URL NameThe-precision-of-float-data-is-incorrect-for-MSSQL
Article Number000186570
EnvironmentProduct : Connect for ODBC SQLServer Wire Protocol driver
Version : All supported versions
Database : SQLServer
OS : All supported platforms
Application : All supported applications
Question/Problem Description
When selecting data from a float field, the precision is incorrect.
Steps to Reproduce
Clarifying Information
Value 7199.39 is returned asĀ 7199.3900000000003
Error Message
Defect Number
Enhancement Number
Cause
Resolution
This is a display issue caused by the application.
Workaround
Bind the value as SQL_CHAR instead of SQL_FLOAT.
Notes
Last Modified Date10/15/2015 10:24 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.