Detail bands beyond first page don't print, but only once

rbuser

Here's the basic setup of my report.

ReportMain
\->SubReport1
\->SubReport2

The user sees "DefaultReport" in a listview component, and can either press
ENTER to preview it or EXPORT to print it to the default connected printer.
The user can navigate to another exam folder (patient exams) and print a
different default report for that patient.

The problem is this: The first time a report is either previewed or printed,
the detail bands for SubRep1 and SubRep2 only print on the first page of
each sub report. ie, Page 1 of 6 looks just fine, 2 of 6 (second SubRep1
page) has the report header, footer and page style but no data, page 3 of 6
(first SubRep2 page) is fine, then 4 - 6 of 6 have no data.

This happens both for preview (which uses a TppViewer component) and for
Print. If print is used, the blank 4-6 pages don't even print out. If I
print a second time, everything is perfect. Further, once one default
report has been previewed/printed one time, all other reports that are
previewed/printed are perfectly fine.

Is there an initialization step I'm missing? Is there a reset or some data
traversal step I don't know about? I assume it's not data because even when
switching to a different report to be generated, it comes out fine so long
as another one has been created already.

My reports use txt pipelines and txt files which are generated upon pressing
print or preview. They are generated each time.

digitalmetaphors

First thing to check is to make sure that the datapipelines are assigned to
the report and subreports.

When is the data access components activated and the data made available to
the report? This process should be completed before Report.Print is called,
is this the case? It sounds like everything is setup correctly, there is
just a timing issue on the first report to be printed. What you can do is
to reduce the complexity. Run our demo txt pipeline reports to verify that
they work. Then remove the txt file generation stuff out of your project,
and use our demos reports instead. The best bet is to make the problem as
small as possible until the problem goes away. Then you can begin to change
the approach and put the project back to gether again piece by piece.


Cheers,

Jim Bennett
Digital Metaphors

rbuser

That was it, thanks Jim. I was assigning the pipelines their filenames in
the BeforePrint event of the main report, however I moved these assignments
out of report generation to before I make the .PrintToDevices call and
everything works great now.

Sometimes it's just so simple. Thanks for the help! I really appreciate
how patient, quick, and helpful you and your company are with your service.

Phil
Spencer Technologies