Subreport shows only 1st record -jitpipeline
Probably a simple answer to this one somewhere too, but I can't find it
(I've looked at the demos, including 139).
I have 3 objects: 1 main object containing a tobjectlist of page objects.
Each page object contains a tobjectlist of row objects. For each page I
want to print every row object.
Before setting autostop to true, my subreport would show a row for every
object in my row list. After, it shows only the 1st row.
I've set the recordcount to the right value, TraverseAllData is True. I've
even added linking fields, although they shouldn't be necessary (unless I'm
missing the point here).
(I've looked at the demos, including 139).
I have 3 objects: 1 main object containing a tobjectlist of page objects.
Each page object contains a tobjectlist of row objects. For each page I
want to print every row object.
Before setting autostop to true, my subreport would show a row for every
object in my row list. After, it shows only the 1st row.
I've set the recordcount to the right value, TraverseAllData is True. I've
even added linking fields, although they shouldn't be necessary (unless I'm
missing the point here).
This discussion has been closed.
Comments
subreport, and now all detail rows show. It does stop automatically anyway,
perhaps because I now have a master-detail linking field.
What do you suppose autostop is actually for on a subreport? Seems
completely useless to me.
A report or childreport will traverse the datapipeline to which it is
attached. In this case, AutoStop should be set to False.
For a report or childreport that is not connected to any datapipeline, there
are two behaviors. If AutoStop is true, a single detail band is generated.
If AutoStop is False, the report will generate detail bands until you
programmatically call Report.Stop from an event-handler.
From the online help:
When AutoStop is set to True, the report will print a single detail band and
then stop.
Defaults to True. When the DataPipeline property is set to a non-nil value,
AutoStop is set to False. If the DataPipeline is set to nil, AutoStop is set
to True.
--
Nard Moseley
Digital Metaphors Corporation
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
tried autostop=true in the first place was because it was suggested in a
techtip as a solution to endless reports. I've now come full circle,
setting autostop to false again in the main report as well as the subreport.
The endless report issue did not recur, but it is a complete mystery how it
got resolved. Perhaps closing the jit pipelines before setting up and
printing solved it. Who knows. I'm glad it seems to work now, but I wasted
alot of time.
Thanks again.
Jeremy