Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Memory usage excessive

edited December 2003 in General
Hi,

I use Report Builder 7.02 with Delphi 5
My report contains about 40 differents queries.
When I preview a report of more than 500 pages a memory usage is greater
than 200Mo. It seems that Report Builder loads all the information in
the memory.

Has anyone managed to reproduce it?
Is it possible to correct this issue by a work arround?

Regards
Fabrice

Comments

  • edited December 2003

    Please do not post questions to support@digital-metaphors.com and the
    newsgroups. Choose one or the other.

    This question is already being handled via support@digital-metaphors.com.

    ReportBuilder opens all queries associated with a report. ReportBuilder
    supports standard Delphi TDataSet data access. It is the responsibility of
    the Delphi data access components and the database engine to manage the
    memory used to build query result sets. ReportBuilder does not load data
    into memory. ReportBuilder calls TDataSet methods such as Open, First, Next,
    etc. There is no low level data access code in RB. RB simply leverages
    Delphi's data access architecture.

    ReportBuilder supports two types of data linking for master/detail data
    relationships:

    1. Standard Delphi TDataSet linking.

    Using the type of linking the detail query will fire each time the master
    dataset records position changes. This may save memory at the cost of
    performance - because the detail query must fire repeatedly.

    2. DataPipeline linking

    This type of linking is used by the RB Data workspace (i.e. DADE). Using the
    type of linking the detail query will fire once and the result set will
    contain all rows required by the entire report.



    --
    Nard Moseley
    Digital Metaphors
    http://www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.