I have a question. Since a user can win time when caching is enabled for a report, why not enable it by default? What is the catch? Or what could be a (or the) problem when I use it for all our reports?
The catch to setting the Report.CachePages property to True is that every page you send to the screen device is cached in memory, taking up more resources. For instance, if you have a 200 page report with a 1 mb image on each page, you could possibly begin to run out of memory depending on the specifications of your machine. You are correct though, with most of today's computers containing 512 mb of RAM at a minimum, it would probably be a good idea to enable this feature by default. Thanks for the feedback.
Comments
The catch to setting the Report.CachePages property to True is that every
page you send to the screen device is cached in memory, taking up more
resources. For instance, if you have a 200 page report with a 1 mb image on
each page, you could possibly begin to run out of memory depending on the
specifications of your machine. You are correct though, with most of
today's computers containing 512 mb of RAM at a minimum, it would probably
be a good idea to enable this feature by default. Thanks for the feedback.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com