Subreports

amortlock

Hi

The client wants the report on one page that has perforations. The report has three different layouts. Each layout refers to 1 to 3 records from the same SQL dataset. And there should only be one copy. For example:
Record 1
Record 2
Record 3
...................................................................................
Record 1
Record 2
Record 3
Some text
...................................................................................
Record 1
Record 2
Record 3
Some different text

The report currently is showing this but is making a new copy for record. So if the SQL only returned 1 record it shows:
Record 1
..................................................................................
Record 1
.................................................................................
Record 1

so there is only one copy. But if the SQL returns 2 records there are 2 copies eg
Record 1
Record 2
..............................................................................
Record 1
Record 2
.............................................................................
Record 1
Record 2
...................
End of first copy
..........................................................
Record 1
Record 2
..........................................................
Record 1
Record 2
.............................................................
Record 1
Record 2
End of second copy
Each layout is in a subreport with the bottom shifting relative to the subreport above. The best so far was when the PrintBehavior is set to pbchild.

Is there any way this can be achieved?

Thanks

Andrew

nicocizik

Hi Andrew,

1. It appears that your main report may also be connected to your dataset which is what would be causing the copies. Try disconnecting your dataset from your main report to avoid this behavior.

2. Since the perforations are likely statically located on each page, I suggest using Fixed style subreports rather than Child. This way each subreport will take up a static amount of space on each page regardless how many records are returned. Be sure to set TraverseAllData to True.

amortlock

Thank you. That fixed it.

Andrew