BUG: Report Loses Data When Stretching Memo Breaks on a Page

Last reviewed: April 30, 1996
Article ID: Q123353
The information in this article applies to:
  • Microsoft FoxPro for Windows, versions 2.5, 2.5a, 2.5b, 2.6, 2.6a

SYMPTOMS

On a FoxPro report, when a memo field stretches and then ends exactly on the last detail line of a page, any field that follows that memo does not print on the subsequent page.

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.

MORE INFORMATION

If a report has the stretching fields memo1, field1, and memo2, the information in field1 will be not print when memo1 ends on the last line of the printable page. For example, suppose the following three lines are separate fields in a Detail band of a report:

   memo1
   "OVERFLOW"
   memo2

"OVERFLOW" is not text, but rather a field expression that is allowed to stretch. If memo1 stretches and ends on the end of one page, the next page will show a blank area where "OVERFLOW" should have printed. This only occurs where each field is stretching and the first memo (memo1) ends exactly on the last printable line of the page.

Steps to Reproduce Behavior

  1. Create a database with two Memo fields:

        memo1 and memo2
    

  2. Add 42 lines to each memo. You can use the following program to populate the memo fields:

    APPEND BLANK FOR i=1 TO 42

          REPLACE memo1 WITH memo1 + "This is Line: "+STR(i)+CHR(13)
          REPLACE memo2 WITH memo2 + "This is Line: "+STR(i)+CHR(13)
    
    ENDFOR

    NOTE: the number of lines required in the memo field to cause the report to break exactly at the end of page may be more or less than 42 depending on the font and printer driver.

  3. Create a report with the following specifications:

        - Two-inch Page Header.
    

        - Eight-inch Detail band.
    

        - One-inch Page Footer.
    

  4. In the Detail band, add the following fields at the specified locations:

       Expression...  Top   Left     Bottom  Right   Height   Width
       ------------------------------------------------------------
       memo1          2.21   0.00    2.39    1.65     0.19    1.66
       "Overflow1"    2.52   0.00    2.70    0.92     0.19    0.93
       memo2          2.70   0.00    2.88    1.65     0.19    1.66
       "Overflow2"    2.96   0.00    3.14    0.92     0.19    0.93
    
       Use 10-point Courier New for the memo1 and memo2 fields and 10-point
       Courier New Bold for the Overflow1 and Overflow2 fields.
    
    

  5. For each field in the Detail band, select the Top--Field Can Stretch radio button.

  6. For each field in the Detail band, check the Print When... and check the When Detail Overflows to New Page/Column check box.

Preview the report and notice that the first page looks correct, but on the second page the first "OVERFLOW" expression does not print.


Additional reference words: FoxWin 2.50 2.50a 2.50b 2.60
2.60a buglist2.50
buglist2.50a buglist2.50b buglist2.60 buglist2.60a
KBCategory: kbtool kbprint kbbuglist
KBSubcategory: FxtoolRwriter


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