Can I use CachePages for a 90+ page report?

rbuser

[apologies if this msg gets posted 2x -- my newsreader is having problems]

I have some simple questions about the CachePages property.

I have used the Tamaracka.com search engine to get as smart as possible
here and have also perused the tech-tips newsgroup.

I am a new RB 6.03 user, but have spent a fairly intensive week developing a report
that reads data from a MySql database using the DBExpress components and
displays the data in a catalog-style report of about 90 pages.

My report previews perfectly when pages are viewed in order. If I skip around, the
the pagination and information on the pages gets mixed up. I have a lot of conditional
events set up so that selected fields are not visible based on the category of item
that is being displayed.

I am figuring that the pagination problems I am having are related to the fact that I
have somehow not programmed the events to fire properly when the report is viewed
out of proper order.

If I set CachePages to true, my problems seem to go away. I can skip around
in the report and all is well. Makes sense to me.

I have read the Help listing for CachePages. Here is my question:

How do I determine if my 90+ page report is occupying (or going to occupy) too much memory
to use the CachePages property. Will the report just slow down as the data is cached to
disk, or will my RB application eventually go belly up with an error?

Since setting CachePages to true is fixing my problem, I'd like to keep it. I just
don't want to program something that will later crash if the report reaches 200 pages or so.

Is there some way that I can determine at what point I will have problems with this setting
set to true?

Thanks

Bill

rbuser

Hi Bill,

when I use pictures, I'll get problems in a Win9x box with larger reports.
But I never had problems in displaying large reports with NT or W2K, even
with pictures.
I would do a simple test with a 1K page report.

regards,
Chris Ueberall;

digitalmetaphors

I wouldn't worry about 90 pages of cached data, or event 200. Once you start
approaching tens of thousands or more than I would maybe start taking memory
usage into consideration. There are a few approaches to finding out how much
memory is actually being used up. The easiest is obviously to use the task
manager and run the report with cache pages off and then with cache pages on
and calculate the difference in memory usage. To get an even more accurate
reading use sizeof and count the number of pages and the number of draw
commands on every page within the publisher cache.

--
Cheers,

Alexander Kramnik
Digital Metaphors