ACC97: Why a Calculated Control Is Blank

Last reviewed: February 4, 1998
Article ID: Q159731
The information in this article applies to:
  • Microsoft Access 97

SUMMARY

Novice: Requires knowledge of the user interface on single-user computers.

This article explains why a calculated control may appear blank.

MORE INFORMATION

When you have a calculation that contains a Null value, the result of the calculation will also be Null. A Null value is not the same as zero; instead, it can be thought of as an unknown value. The result of adding an unknown value to a number is unknown.

When you have fields that contain Null values, you can create an expression that converts the Nulls to zero. You might do this if you want the records containing Null values to be included in an aggregate (totals) calculation, or if you want to prevent an expression from resulting in a Null value when a field that is referenced in the expression contains Nulls. To convert Null values to zero, use the Nz() function. For example:

   Nz([Subtotal])+Nz([Freight])

REFERENCES

For more information about handling Null values, search the Microsoft Access Help Index for "blank fields, Null values," or ask the Microsoft Access 97 Office Assistant.

Keywords          : kbprg kbfaq
Version           : 97
Platform          : WINDOWS
Hardware          : x86
Issue type        : kbtshoot


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


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