Report with DataLink very slow

rbuser

I was made a report with 3 querys linked (master - detail - detail) and when
the RB open of all query's all data of detail query's are selected same the
master query was filtered.

I have to filter detail query's too?? or only master?? How made link??


What option I have use???
1-Include only those records from MASTER QUERY for which matching DETAIL
QUERY records can be found.

or

2-Include all records from MASTER QUERY, regardless of whether any matching
DETAIL QUERY records can be found.

Uildenei
Fco Beltr?o - Paran? - Brasil

nardmoseley

You can add search criteria to the master query so that only the master
records that you want to include in the report are retrieved from the
database. ReportBuilder will generate special linking SQL for the detail
queries that limits the number of detail rows retrieved as well. See the
article below.

You may need to add some indexes to your database tables to speed the query
execution.

With ReportBuilder linking each query is only fired a single time for the
entire report. This is different from Delphi TDataSet linking which fires
the detail query each time the record position in the dataset changes.
ReportBuilder's linking provides faster performance for reporting.

-------------------------------------------
Tech Tip: Linking DataViews
-------------------------------------------

Overview
---------

Linking DataViews in the ReportBuilder Data workspace (DADE), requires that
the detail data be sorted by the linking fields. When DataViews are linked,
DADE generates special linking SQL for the detail DataView. The linking SQL
(Magic SQL) can be viewed by positioning the mouse over the DataView window
and pressing Ctrl + Left Mouse button. The results of the Magic SQL query
can be viewed by pressing Shift + Left Mouse button.

ReportBuilder's DataPipeline architecture includes support for linked data
traversal. Whenver the record position of the master data changes, the
traversal logic compares the master and detail field link values and then
determines where to locate the record position for the related detail data.
The linking logic will only work properly if the Database engine's collation
of the detail query result set is in sync with ReportBuilder's internaly
field link comparison logic.


--

rbuser

Nard,

not resolved my problem with your soluction ... you have a idea of the I
need do?


Uildenei