BUG: SQL Debugger Displays Incorrect Value for Float Variables

 Last reviewed: May 21, 1997
Article ID: Q165419
The information in this article applies to:
  • Microsoft Visual C++, 32-bit Enterprise Edition, version 5.0

SYMPTOMS

The value of FLOAT variables inside the SQL Debugger is displayed incorrectly for any value other than zero.

For example, a float that you expect to contain the value 1.1 is displayed as the value 4.6508221013814e-104.

RESOLUTION

This only effects the display of FLOAT values. Modify the values of FLOAT variables with the debugger and the changes will be made correctly.

To workaround this, you can assign the value of the FLOAT variable to a CHAR variable and examine the CHAR variable in the debugger. For example: 

   DECLARE @floatVar FLOAT
   DECLARE @strVar CHAR (10)

   SELECT @floatVar = 1.1
   SELECT @strVar = CONVERT ( CHAR(10), @floatVar )

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords : kbprg vcbuglist500 VCEntIss VCEntSQLDebug kbbuglist
Version : 5.0
Platform : WINDOWS
Issue type : kbbug

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