Am 18.03.2021 um 16:06 schrieb Andreas Frieß via fpc-pascal:
Am 18.03.2021 um 14:24 schrieb Michael Van Canneyt via fpc-pascal:
In that case, you must put lReportOLData2 on a separate design page.
So:
* Add a design page (page 1) to the report.
* Do what you need with lReportOLData1 on this page.
* Add a second design page (page 2) to the report
* Do what you need with lReportOLData2 on this page.
That should be it.
Michael.
It is a joke, every ReportData need a new page.
The issue is, fpreport handle the Databand not correct.
All have no Masterband set
A ) If i bound no Data to a Databand, automatic the dataset of the
parent (Page) is used -> Ok yet -> Dataloop of parent is used
B ) If i bound Data to a Databand and it is the same like the parent
(page) -> Ok -> Dataloop of parent is used
C ) If i bound Data to a Databand and it is not the same like the parent
-> Not Ok -> the first it is handled like B - it should use their own
dataloop
You can make this with a fake working. Make a dummy Databand with a
Dataset with ONE entry only. Then bound the datasets as childdatasets
and it works.
You see the problem with the FPReport Designer too.
- Make a new report
- add two datasets (eg, csv with valid data)
- add PageheaderBand, TitleBand and PageFooterband
- add a Databand bound the Data1 to it
- add a Databand bound the Data2 to it
Make a Report Preview -> only the contend of the first dataset is shown.
I will file a bug
Andreas
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
