Filter
Top Products
Working with nested reports
328 DataWindow .NET
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. DataWindow Designer retains this compiled form of the
SELECT statement for use in subsequent retrieval requests.
Requirements for
reusing the compiled
SELECT statement
To enable DataWindow Designer 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 DBParm to 0,
which is the default.
• You must enable caching in the database profile. Set the SQLCache
DBParm parameter to the number of levels of nesting plus 5.
For more information, see the description of the SQLCache and
DisableBind DBParm parameters in the online Help.
Nested reports in composite reports
If the base report is a composite report, you need to define retrieval arguments
for the composite report before you can supply them to the nested report.
In the Properties view for the composite report, select the General page. Then
define the retrieval arguments that the nested report needs, taking care to
specify the correct type.
❖ To supply a retrieval argument value from the base report to the nested
report:
1 Make sure that the nested report has been set up to take one or more
retrieval arguments.
See “Placing a nested report in another report” on page 321.
2 Select the nested report and then select the General page of the Properties
view.