>Hello All,
>
>I've run into an interesting problem printing reports. I run low on resources after running REPORT FORM mysummary FOR invdate <= dDate NOCONSOLE TO PRINTER PROMPT PREVIEW. I don't even have to print, just looking at the preview is good enough. I searched the MS KB articles and came up with article Q232660. It is similar to what I'm experiencing, however, I don't print any bitmaps. It's a simple form with lines as the only grphics elements. I also don't need so many iterations - under 50 is enough to do it. Generally i'll be previewing a lot when I'm creating or editing teh layout and contents of a report, and I will get a blue screen after so many previews, or when I attempt to modify a form later on.
>
>I am running VFP6 SP5 on Win98. When my new notebook arrives, some time between the 29th and 31st (if all goes well), I will then be running on Win2k, - SP2 if I can help it.
>So far I don't thikn I have experienced this problem with other reports. Just one in particular but I may not have previewed quite as much as this one? or the FOR conditions were different.
>
>Has anybody else experienced anything similar? This puzzles me and is a little annoying because low resoureces really messes with how windows functions. (Basically it stops functioning :-/ )
>
>---
>Jonathan Chan

1st, TO PRINTER and PREVIEW are different options. only one or the
other will be used. but that is unlikely to be your resource leake.

more like, check your code the builds the report for variables that
are not being released. especially, large strings or classes. be sure
to also check any UDF's called implicitly from your report for the
same thing.