We have a problem with a report (Stimulsoft Reports .NET) and we think it is a bug. It is easy to reproduce also in the newest version.
Create three datasources
Source1 (Header)
Source2 (Position section 1 with Relation1 to source1)
Source3 (Position section 2 with Relation2 to source1)
Create a report structure like this:
Group Header with a group condition, so that every record from source1 defines a group
and with property "StartNewPage=true"
Databand1 (Source1)
Group Footer
Databand2 (Source2)
Databand3 (Source3)
The layout should look like this:
Address from a header record (databand1)
Positions from source2
Positions from source3
Text of the group footer
etc. with the next address on a new page.
Problem: If a header record has a number of related positions of source2 (or source3) which determines a page break, the report runs in an endless loop. This is caused by the group header band, not by the StartNewPage-property in this band.
If one have only one position section there is an obvious workaround, because one can use only one databand with a group condition based on a field of the relation.
Endless loop
Endless loop
Hello,
Please set the EngineVersion property of your report to EngineV2. This will turn on new report engine, which solves many problems on th old one and works much quicker.
Please note that, instead of the StartNewPage property, the NewPageBefore and NewPageAfter properties are used in EngineV2.
Thank you.
Please set the EngineVersion property of your report to EngineV2. This will turn on new report engine, which solves many problems on th old one and works much quicker.
Please note that, instead of the StartNewPage property, the NewPageBefore and NewPageAfter properties are used in EngineV2.
Thank you.
Endless loop
Thank you. Indeed with Engine V2 no endless loop occurs but the following problem.
If a page header or page footer is included no data is printed on the first page, only the page header text or page footer text. If one set the property "PrintOn" to "ExceptFirstPage", no empty page occurs, but it seems that this property is based on the system variable PageNumberThrough and not PageNumber. This is not the expected behavior, because "first page" refers to the first page of the document and not the first of all pages.
If a page header or page footer is included no data is printed on the first page, only the page header text or page footer text. If one set the property "PrintOn" to "ExceptFirstPage", no empty page occurs, but it seems that this property is based on the system variable PageNumberThrough and not PageNumber. This is not the expected behavior, because "first page" refers to the first page of the document and not the first of all pages.
- Attachments
-
- 437.Bug-Report.mrt
- (20.72 KiB) Downloaded 149 times
Endless loop
Hello,
Can you please send us a sample report with data, which reproduces the issue?
Also pay your attention that if the PrintOn property of the component is not set to AllPages, then for correct report rendering double pass should be enabled.
Thank you.
Can you please send us a sample report with data, which reproduces the issue?
Also pay your attention that if the PrintOn property of the component is not set to AllPages, then for correct report rendering double pass should be enabled.
Thank you.
Endless loop
I attached an mrt-file to my last posting. The data refers to our database, but the structure ist very simple, so you can include your own datasource.
Endless loop
Hello,
Thank you.
Please set the KeepGroupHeaderTogether property of GroupHeader to false.hgquade wrote:Thank you. Indeed with Engine V2 no endless loop occurs but the following problem.
If a page header or page footer is included no data is printed on the first page, only the page header text or page footer text.
Please set the NumberOfPass property of your report to DoublePass.hgquade wrote: If one set the property "PrintOn" to "ExceptFirstPage", no empty page occurs, but it seems that this property is based on the system variable PageNumberThrough and not PageNumber. This is not the expected behavior, because "first page" refers to the first page of the document and not the first of all pages.
Thank you.