ACC95: Properties Reset on Landscape Report with Snaking Columns

 Last reviewed: June 17, 1997
Article ID: Q170219
The information in this article applies to:
  • Microsoft Access 7.0

SYMPTOMS

In Microsoft Access 7.0, when the column width of a report with snaking columns exceeds the page width, and the page orientation is set to Landscape, the properties of the report will be reset and the report will no longer contain snaking columns.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access version 7.0. This problem does not occur in Microsoft Access 2.0 and 97.

MORE INFORMATION

Steps to Reproduce Problem

CAUTION: Following the steps in this example will modify the sample database Northwind.mdb. You may want to back up the Northwind.mdb file, or perform these steps on a copy of the Northwind database.

  1. Open the sample database Northwind.mdb.

  2. In the Database window, click the Reports tab.

  3. Open the Products By Category report in Design view.

  4. In the CategoryName Header section, resize the Units In Stock label width to 3.5 inches.

  5. On the File menu, click Print Preview.

  6. On the File menu, click Save.

  7. Close and then reopen the report. You receive the message that the section width is greater than the page width. Click OK.

    Note that the report no longer contains the snaking columns and the page orientation of the report has been changed to Portrait. Also, the property settings for the margins, column widths, and heights in the report have been reset.

Keywords : kbusage RptLayou RptProb
Version : 7.0
Platform : WINDOWS
Hardware : x86
Issue type : kbbug
Resolution Type : Info_Provided

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