Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Previews fine but prints endless blank pages

edited January 2002 in General
Hello,

I have a report that previews fine, but generates endless blank pages when I
send it to a printer. (Actually, the first page prints OK, but is followed
by endless blank pages.) This happens with both an HP LaserJet 4 and with
the Adobe Acrobat PDFWriter printer, so I suspect it is a problem with my
report rather than with the printer drivers. When previewing, I can jump to
the last page and everything behaves correctly.

My setup:
ReportBuilder 6.03
Delphi 6 / Update Pack 1
Windows 2000 Pro SP2

The report itself is a bit unusual. Each record of the dataset must
generate a cover letter and one or more enclosures. We are doing this using
multiple subreports. We control which enclosures (subreports) are generated
by setting the Visible property of the appropriate subreports in the
BeforePrint event handler for the detail band of the main report.

I've already reviewed the Tech Tip "TroubleShooting: Report Prints Endless
Pages," but still have not been able solve the problem. Any help would be
appreciated.

--David Body / Big Creek Software, LLC

Comments

  • edited January 2002
    The HP LaserJet 4 is a good driver.

    Make sure that the subreports have datapipelines connected to them and are
    non nil.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited January 2002
    Jim,

    When I assign datapipelines to all the subreports, I get endless (nonblank)
    pages in Print Preview. Also, the pages are no longer in the desired order.
    We get all of the cover letters, followed by all of the enclosures, and the
    whole thing seems to be repeated endlessly. What we want is a cover letter
    followed by an enclosure, then the next cover letter followed by the next
    enclosure, etc. It also needs to stop after everything has been printed
    once.

    Any other suggestions?

    --David Body / Big Creek Software, LLC

  • edited January 2002
    "David Body" wrote in message
  • edited January 2002
    Thanks for the suggestion, but as I mentioned in my original post, I have
    already done this.

  • edited January 2002
    "David Body" wrote in message
  • edited January 2002
    Jim,

    We are still looking for a solution to this problem. Do you have other
    suggestions?

    --David Body / Big Creek Software, LLC


  • edited January 2002
    Be sure you are setting the Visible property of the subreports. Set the
    visibility of the subreports, which aren't going to print, to False. Set
    the subreports, which have a non-nil pipeline, to Visible = True.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited January 2002
    Jim,

    Thanks. It turns out that the problem was the result of our having
    inadvertently set the ParentPrinterSetup property to true on all of our
    subreports. Setting this property to false on all but the first subreport
    solved the problem.

    By the way, I don't think we ever explicitly set this property. Each of the
    subreports was developed separately, and later they were combined into a
    larger report. Apparently this property setting carried over in the
    process.

    Thanks to Kevin Kennedy of Digital Metaphors tech support and Dave Kair of
    the Iowa Legislative Fiscal Bureau for independently figuring this out for
    us.

    --David Body / Big Creek Software, LLC

This discussion has been closed.