SubReport only printed the second time
Hello,
i have created a report with some subreports (connected to different
ppJITPipelines; PrintBehaviour: pbSection) on the main page. Some of
these subreports contains other subreports (also connected to
ppJITPipelines). I want the user to choose, which parts of the report
will be printed. So I switch the subreports on or off using their
visible attribute. I set the RecordCount attribute of the subreports
with a datapipeline in the ppReportBeforePrint method. If I print the
report the first time with some subreports visible, there is nothing
wrong. If I switch the visible attribute of another subreport with a
datapipeline to true and print again, the new subreport will not be
printed. But if I start the printing again, all will be fine. Do you
have any idea, where i made a mistake? It only concerns subreports with
a datapipeline.
ppReport: CachePages: False; PassSetting: psTwoPass
Torsten
i have created a report with some subreports (connected to different
ppJITPipelines; PrintBehaviour: pbSection) on the main page. Some of
these subreports contains other subreports (also connected to
ppJITPipelines). I want the user to choose, which parts of the report
will be printed. So I switch the subreports on or off using their
visible attribute. I set the RecordCount attribute of the subreports
with a datapipeline in the ppReportBeforePrint method. If I print the
report the first time with some subreports visible, there is nothing
wrong. If I switch the visible attribute of another subreport with a
datapipeline to true and print again, the new subreport will not be
printed. But if I start the printing again, all will be fine. Do you
have any idea, where i made a mistake? It only concerns subreports with
a datapipeline.
ppReport: CachePages: False; PassSetting: psTwoPass
Torsten
This discussion has been closed.
Comments
those subreports to true so that they have a chance to refresh the data when
you print again. Try upgrading to RB6.03 if you aren't using it already to
test if there could be a potential bug in the older version of the engine.
--
Cheers,
Alexander Kramnik
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com