How Are Invisible Sub-Reports Handled?
I have RB 7.02 and was wondering what does RB do with invisible
(visible=false) sub-reports. Specifically, is every component within the
report generated whenever the report is generated or is only those
components that are within the visible report(s) generated? The reason I
ask is that I have several reports that have several sub-reports each
containing several hundred components. If only visible sub-report
components were dealt with it would seem to me that the reports would be
generated much faster. As it seems right now, every component is generated
in the report, but they're not visible.
Also, how is it possible to determine which component belongs to which
sub-report. I have a routine that evaluates each component to determine how
it should be displayed. What I would like to do is not evaluate those
components that are on an invisible sub-report.
Thanks,
Jeff Kreider
(visible=false) sub-reports. Specifically, is every component within the
report generated whenever the report is generated or is only those
components that are within the visible report(s) generated? The reason I
ask is that I have several reports that have several sub-reports each
containing several hundred components. If only visible sub-report
components were dealt with it would seem to me that the reports would be
generated much faster. As it seems right now, every component is generated
in the report, but they're not visible.
Also, how is it possible to determine which component belongs to which
sub-report. I have a routine that evaluates each component to determine how
it should be displayed. What I would like to do is not evaluate those
components that are on an invisible sub-report.
Thanks,
Jeff Kreider
This discussion has been closed.
Comments
When you set a subreport's visibility to False, the components inside the
subreport (ie. the draw commands) will not be created and therefore not
generated.
However... if you are linking your queries, the detail dataset will be
opened and traversed every time you traverse through the master dataset.
This would be what is slowing down your report. I would suggest using
DataPipeline links rather than query links to link your master and detail
datasets. This then does not require the detail dataset to be opened for
every master record.
- If you would like to go even further and only open a detail dataset when
the user decides he/she needs to, (say in a drill down report), you can do
this by using the method in the example provided below.
http://www.digital-metaphors.com/tips/DrillDownManualDetail.zip
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com