Rich,

Could you take some time to summarize the performance solutions you've found and post to the wiki?


>
>Doug,
>
>I have been doing a lot of performance testing with the VFP 9 Report Engine and as Craig mentioned in his post, that when rendering a Preview all of the pages are rendered into memory as EMF images and resolution does come into play. The resolution affects the rendered images.
>
>I would be very curious to know what the performance is when rendering your report using the Mind's Eye Report Engine Control using the new MERE_ReportListener class. MERE does not store it's pages as EMF images in memory and images are stored as file names pointing to the image file and aren't rendered until the page is previewed or printed. When VFP is rendering pages as EMF images, any images must be rendered and saved into each EMF page in memory. So, not only is a lot more memory consumed, but there is also a performance hit.
>
>Some things you can do to speed up a native VFP Preview when using SET REPORTBEHAVIOR 90, is to use the NODIALOG clause on the REPORT FORM command to suppress the PROGRESS BAR displayed by the new engine. The Progess Bar displayed in VFP 9 increases Report Preview time almost 10 fold or more.
>
>If you really want the old speed back, you can use SET REPORTBEHAVIOR 80.