Stimulsoft Report looping
Posted: Fri Sep 18, 2009 3:44 am
Hello,
We had a problem yesterday where Stimulsoft was looping.
We are using versions 2009.2.422.0 of your dlls - I know there is a new release available but I have not tried it yet. I could also potentially create a small c# application demonstrating the problem but first wondered if you are aware of it or in fact need any more information.
We pass some data into a report and the data is a Collection where each A element contains a Collection. On the report there are two data bands, one for A and one for B and the report lists the A elements with its B elements shown underneath. In the case where it was looping we had just one A element in the collection, with 50 or so B elements underneath it. The main thing was there were too many B elements to fit onto a single page.
When the report was run it just kept generating thousands of pages and presumably would eventually run out of memory. We solved it by setting the CanBreak property on the B databand to true. It therefore looked like it was trying to fit all the B elements onto a single page, realised they wouldn't fit, tried to fit them onto the next page, realised they would not fit there either, created another page and so on. Any thoughts ?
Many thanks
Robin
We had a problem yesterday where Stimulsoft was looping.
We are using versions 2009.2.422.0 of your dlls - I know there is a new release available but I have not tried it yet. I could also potentially create a small c# application demonstrating the problem but first wondered if you are aware of it or in fact need any more information.
We pass some data into a report and the data is a Collection where each A element contains a Collection. On the report there are two data bands, one for A and one for B and the report lists the A elements with its B elements shown underneath. In the case where it was looping we had just one A element in the collection, with 50 or so B elements underneath it. The main thing was there were too many B elements to fit onto a single page.
When the report was run it just kept generating thousands of pages and presumably would eventually run out of memory. We solved it by setting the CanBreak property on the B databand to true. It therefore looked like it was trying to fit all the B elements onto a single page, realised they wouldn't fit, tried to fit them onto the next page, realised they would not fit there either, created another page and so on. Any thoughts ?
Many thanks
Robin