Visual Basic INT Function Returns Incorrect Value

Last reviewed: July 29, 1997
Article ID: Q115395

The information in this article applies to:
  • Microsoft Visual Basic Programming System, Applications Edition, version 1.0
  • Microsoft Excel for Windows, version 5.0
  • Microsoft Excel for Macintosh, version 5.0
  • Microsoft Project for Windows, version 4.0

SYMPTOMS

In a Visual Basic Programming System, Applications Edition procedure, the Int function returns the incorrect value when the number you use in the function is a Double data type value. For example, the Integer value of 201 should equal 201, but the Int function may return the value 200.

CAUSE

This behavior occurs because the Int function incorrectly truncates the number value when the number is a Double data type (double-precision floating-point).

Note that this behavior does not occur with Integer type or Single type number values.

RESOLUTION

To work around this problem, use either of the following examples:

Microsoft provides examples of Visual Basic procedures for illustration only, without warranty either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. This Visual Basic procedure is provided "as is" and Microsoft does not guarantee that it can be used in all situations. Microsoft does not support modifications of this procedure to suit customer requirements for a particular purpose. Note that a line that is preceded by an apostrophe introduces a comment in the code--comments are provided to explain what the code is doing at a particular point in the procedure. Note also that an underscore character (_) indicates that code continues from one line to the next. You can type lines that contain this character as one logical line or you can divide the lines of code and include the line continuation character. For more information about Visual Basic for Applications programming style, see the "Programming Style in This Manual" section in the "Document Conventions" section of the Visual Basic "User's Guide."

  • Use the CInt function instead of the Int function as in the following example:

          Sub IntTest()
             Dim x as Double
             x = 100 * 2.01
            ' Display x in a message box
            ' Note that MsgBox displays value of x as string expression
            ' displays value of 201 at this point
             MsgBox x
            ' Display the Integer value of x in a message box
            ' (should equal 201)
             MsgBox CInt(x)
          End Sub
    
       -or-
    
    
  • Use the Str function to return a string representation of the number before using the Int function as in the following example:

          Sub IntTest()
             Dim x as Double
             x = 100 * 2.01
            ' Display x in a message box
            ' Note that MsgBox displays value of x as string expression
            ' displays value of 201 at this point
             MsgBox x
            ' Display the Integer value of x in a message box
            ' (should equal 201)
             MsgBox Int(Str(x))
          End Sub
    
    

STATUS

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

Keywords          : kbcode kbprg
Version           : 1.00
Platform          : WINDOWS


================================================================================


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