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

High memory usage

edited December 2008 in DADE
Hello all,

First my environment:
D7 RB 903 with Oracle (daDOA).
I have a quite big (~2200 pages) report.
This report reads a lot of data. It works fine
but the problem is that it uses a lot of memory (till 1gb)
and quite a lot of my customers still have old machines with not so
much memory installed ...
On these machines the program stops with an "out of memory" error.
May you have tips/ideas to reduce this memory request ?
Thanks for any help
Bye
Nicola

Comments

  • edited December 2008
    1. Try using the Report.CacheManager.CacheType poperty to specify file based
    caching. This affects the report engine.

    uses
    ppTypes;

    myReport.CacheManager.CacheType := ppctFile;


    2. Check the Report.PassSetting. Using psOnePass will be more efficient,
    however the design of the report may be relying upon psTwoPass to work
    correctly, so might not be an option.

    3. You could try generating the report to an archive file (.raf). That might
    be less memory intensive. Then you could preview/print from the archive.

    4. On the data access side of things I do know whether DOA has any config
    options to use file versus memory - you could send a question to DOA tech
    support.

    5. When linking DataViews in DADE, all records for the entire report are
    selected at the beginning. This provides the fastest performance. With RB
    11 there are new options to specify parameterized linking - so that the
    detail query fires each time the master record position changes. That would
    use less memory.


    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

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