ACC1x: Query Results in "Overflow" Error Message

Last reviewed: May 28, 1997
Article ID: Q104488
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SYMPTOMS

When you run a query an "Overflow" error message is returned.

CAUSE

This error message can occur when you use And or Or with numbers greater than 32768. For example, the following expression in the field row of a query will cause an the error:

   Expr1: 32768 and 0.

NOTE: There are other causes of the Overflow error that can be avoided by using the correct data types for variables, or by modifying the expression that causes the error. This behavior is by design, and is explained in the Help topic for the Overflow error. These errors include:
  • Dividing one number by another number such that the result is larger than the data type can hold. For example,

          Dim MyVal As Integer
          MyVal = 32767 / 0.1
    

    would result in setting MyVal to 327,670, which exceeds the maximum integer size of 32,767.

  • Multiplying two numbers such that the result is larger than the data type can hold.
  • Dividing any number by zero.

STATUS

This problem no longer occurs in Microsoft Access version 2.0.


Keywords : kbusage QryParm
Version : 1.0 1.1
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : kbfix


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