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

hundreds of pages printed instead of one...

edited August 2002 in General
Hello,

I'm trying to print the content of an Edit field, using JITPipeLine.
Here is the code I use :
ppReport1.DeviceType := 'Screen';
ppReport1.ShowPrintDialog := True;
ppJITPipeLine1.RecordCount := 1;
ppReport1.Print;
This works fine in Preview mode : when I click on "LAST", it stays on record
1

but when I use :
ppReport1.DeviceType := 'Printer';
ppReport1.ShowPrintDialog := False;
ppJITPipeLine1.RecordCount := 1;
ppReport1.Print;
hundreds of pages are printed...
If I just change this :
ppReport1.ShowPrintDialog := True;
and then ask for pages 1-3, only one page is printed...

Can somebody please tell me what I am doing wrong ?
(I work with RB pro 6.03 with patch...)

Thanks !

Comments

  • edited August 2002
    We don't know what else is going on in this report. Are there subreports? I
    can send you a patch for 6.03 which addresses issues of the report not
    regenerating when printing to the printer (it prints off of the page cache
    created for the preview). There is also an article in the tech-tips
    newsgroup (in the general thread) which describes ways that you can get
    infinite pages in a report.


    Cheers,

    Jim Bennett
    Digital Metaphors

  • edited August 2002
    Hello,

    I do not get any messages in the tech-tips newsgroup.
    Where can I find the article about infinite pages in a report?

    Thanks
    Georg

  • edited August 2002
    Set your newsreader to display older messages. Then redownload the
    newsgroup. Here is the article:

    ------------------------------------------------------
    Article: TroubleShooting: Report Prints Endless Pages
    ------------------------------------------------------

    Occasionally, we have customers state that their reports are in some
    infinite state where page after empty page prints forever.

    There are a few items to check when this occurs.

    The TppReport.AutoStop property is the first thing to check. If this is
    false when the DataPipeline property is unassigned, the endless report
    will be the result. AutoStop is automatically set to True when
    DataPipeline is set to nil, but it is possible to set it back to False.
    Check for instances in your code where you might have created this
    condition.

    Another thing to check is that all subreports in your report have their
    DataPipeline set. When a subreport does not have its pipeline set, you
    will sometimes see a condition where the first detail record prints and
    then you get blank pages.

    Another, non-data related cause can sometimes be your margin settings.
    If you have stretching bands that need to overflow to the next page, if
    your margins are too tight, sometimes the report engine will endlessly
    overflow to the next page trying to fit the overflow material.

    Still another cause might be having a statically positioned control, set
    to ReprintOnOverFlow, in the same band with a stretching control. For
    instance, if you have a memo set to stretch and in that same band, a
    label control set to ReprintOnOverFlow, then on every page after the
    first, the memo will begin to print after the label control. If the
    label is placed low enough that the memo has no room to print, the
    report will forever be trying to print the overflowing memo on the next
    page.

    --
    Tech Support mailto:support@digital-metaphors.com
    Digital Metaphors http://www.digital-metaphors.com

    --
    Cheers,

    Jim Bennett
    Digital Metaphors

This discussion has been closed.