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

Out of memory problem

edited February 2003 in End User
Hi

I am using RB 7 Enterprise D7, D7 Professional and
IBX7.04. IB 6.0.1.6 Open Edition.

I have created an end user solution which are crashing with out of memory
errors when lost of data are involved.
I have clients whose retail databases can have 50 000 stock items easily.
Example:
I design a simple report with only a detail band and put on only 3 dbtext
components for the following fields: stockcode, descr, sizedescr .
Using a custom search page I generate sql for the report. The result of the
sql can be = 1 record or all records depending on options chosen for
the report. If I choose options that causes all records to be displayed on
report it generates about 330 pages and then crashes with an out of memory
error.
If I change sql so that only say a 100 pages is generated then this error
does not occur.

How do I solve this problem as I have clients who are complaining about this
and wants to display all data on certain reports.

TIA

Ruaan

Comments

  • edited February 2003
    We test RB using Sleuth QA Suite for leaks. We are not aware of any leaks.
    Run a memory watching tool such as TP Sleuth QA or Automated QA. This will
    tell you where the leak is in your code. If you can reproduce the problem
    using a demo database, such as DBDEMOS of Northwind Traders, without your
    code and just using Report.Print then send us the example to
    support@digital-metaphors.com


    Cheers,

    Jim Bennett
    Digital Metaphors


This discussion has been closed.