ACC1x: Invalid Results in Subreport When CanGrow = Yes

 Last reviewed: May 14, 1997
Article ID: Q98794
The information in this article applies to:
  • Microsoft Access version 1.0

SYMPTOMS

If a control in a subreport uses an expression or aggregate function and its CanGrow property is set to Yes, Microsoft Access does not calculate the value of the field correctly.

For example, assume your database contains a table named Test that has a text field called TestColumn containing the following values: 

   TestColumn
   ----------
   Mickey
   Donald
If you create a report with a single text box (Field1) containing the expression 

   =IIf(IsNull([TestColumn]),"N/A",[TestColumn])
and you set the CanGrow property for Field1 to Yes and then embed that report as a subreport, you get the following incorrect results: 

   Donald
   Donald
If the calculated subreport field contains an aggregate function, instead of a text-based expression as above, the subreport displays incorrect numeric values.

RESOLUTION

Make sure that the CanGrow property of subreport fields that use expressions or calculations is set to No.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access version 1.0. This problem no longer occurs in Microsoft Access version 1.1.

Keywords : kbusage RptSub
Version : 1.0
Platform : WINDOWS
Hardware : X86
Issue type : kbbug
Resolution Type : kbworkaround

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