>>>Hi All,
>>>
>>>I already asked for help in thread #1319611, but so far to no avail. So I ask again.
>>>
>>>On a report I must show detail1 data on a new page and detail2 data on a next page. I succeed in printing detail1 data on a new page and detail2 data on a next page, but a detail2/next page is even generated if there are no detail2 data to print. It gives an empty page (apart from a header/footer).
>>>
>>>For this case I have created a zipfile. It can be downloaded here: http://hyp.viafox.nl/ut/testcase_emptypages.zip
>>>
>>>I have tried all combinations I could think of. Nothing helps, or it creates another issue. Help is very much appreciated.
>>
>>Hi Peter,
>>
>>Have look at www.Report-Sculptor.com
>>
>>It gives you total control over report content writing.
>>Read entire home page; in there you will see example (oop reporting) of combining form objects (containers) with script, which amounts to totally free OOP report composition.
>>
>>http://www.report-sculptor.com/#CombineScript
>
>Hi Sergio,
>
>Wow, that was impressive. I have read it all and will download it and try the demo first. The concept feels like a new paradigm to me. I cannot anymore remember the time I took control of the reporting loop using ?, ?? and the like. It even may be the case that I never did it. A new paradigm is often difficult for people to grasp.
>
>The current paradigm (Report Designer) is: Prepare all data and then off you go with the REPORT FORM command. And sure, there is some control during the run, but that's minor only.
>
>As I grasp it now, your paradigm is: Write a LOOP that contains code to get certain data and other code that creates the next part of the report.
>
>A remarkable feature of your Report Sculpture is that we can use SCXs instead of the Report Designer. Those forms not only contain the layout of report sections, but also the logic to generate the contents. Wow, what a concept!

Hi Peter,

Print-as-you go (?/??) is not main idea at all, but just another possibility.

Please, read carefully home page and you will realise that there is much much more going on in ReportSculpor ;)

If you look at sublink I sent you You will see that you can use visual objects directly to compose report sections
without having to 'sweat' with .lf() / .Lw() / .Eject() etc.

So you simply stage flow of data, and then point to containers on form (which not necessarily have to be visible!)
to serve as actul 'bands'
See also sample (form 09) which gives you also organised run trough data (grouping)
and also prg samples (08,09,10) of how to wrap form based report into plausible implementation.

And yes, you can think of ReportSculptor as completely new reporting paradigm. FRX becomes just another 'design element'
next to other design concepts.

More the merrier ;)



HTH & Thank You for compliments