I changed the event to BeforePrint in both report examples. I did NOT CHANGE the
RepeatStyle since I want to do more testing. The memory exception still occurs, but I think in a
different place that when I first sent you the example.
I also updated the queries to create a better approximation of the type of data that is returned in
the real queries.
I added 2 new tests:
1) Exporting to RTF shows corruption, similar to pdf export.
2) An example where exporting to rtf caused our app to become unresponsive. The test example runs for ~2.5 minutes on my dev machine. It is an 80 page report so I think it should
run faster. On a vm with 2 G memory it ran ~4 minutes.
In Summary:
Attached is a test program that I used to reproduce issues we are seeing in test and at customer sites.
1) The out of memory exception
2) The pdf corruption (which you have identified as fixed, but not release) . On my
development machine, it occurs around page 50.
3) We also see rtf corruption (which may be related to #2). On my development machine, it
occurs around page 50.
4) The export to rtf which is causing our app to become unresponsive and in my testing ran for
2.5 minutes. On a vm with 2G memory, it ran ~4 minutes.
Thanks,
Steve