Specifications

CHAPTER 11 Using Nested Reports
Users Guide 357
Adding another nested report to a composite report
After you have created a composite report, you might want to add another
report. The following procedure describes how. For information on adding a
nested report to a report that is not a composite report, see “Placing a related
nested report in another report” on page 351 or “Placing an unrelated nested
report in another report” on page 354.
❖ To add another nested report to a composite report:
1 Open the composite report.
2 Select Insert>Control>Report from the menu bar.
3 Click in the Design view where you want to place the report.
The Select Report dialog box displays, listing defined reports in the
current library.
4 Select the report you want and click OK.
A box representing the report displays in the Design view.
Supplying retrieval arguments to relate a nested report to its base
report
The most efficient way to relate a nested report to its base report is to use
retrieval arguments. If your nested report has arguments defined, you use the
procedure described in this section to supply the retrieval argument value from
the base report to the nested report. (The procedure described is part of the
whole process covered in “Placing a related nested report in another report”
on page 351.)
Why retrieval
arguments are
efficient
Some DBMSs have the ability to bind input variables in the WHERE clause of
the
SELECT statement. When you use retrieval arguments, a DBMS with this
capability sets up placeholders in the
WHERE clause and compiles the SELECT
statement once. InfoMaker retains this compiled form of the
SELECT statement
for use in subsequent retrieval requests.
Requirements for
reusing the compiled
SELECT statement
To enable InfoMaker to retain and reuse the compiled SELECT statement:
• The database interface must support binding of input variables.
• You must enable binding support by setting the DisableBind database
parameter to 0, which is the default.