>
>How many times did you have to run the report before you observed the output corruption? Did you, in fact, observe the visual effects described by your users?
>

No, I didn't view the same corruption they saw (my machine has a LOT more memory than them, and the corruption is actually happening when printing). They weren't exactly sure how many times they ran the report - the estimate they gave me was 30-40 times.

>Does a CLEAR ALL free up the memory?
>

Hmm...I didn't try.

(a few minutes later)

I just tried it and no, the memory usage level never returns back down to it's original level, even with a CLEAR ALL.

>What tests are you using to verify the memory being used?
>

Just firing up the task manager and watching the memory usage. It slowly climbs each time I run the report.

More specifically, what I'm seeing is, the memory usage climbs each time the report is being generated (no surprise there). Once the report is done, memory usage drops but it's still slightly above where it was the previous time.