nested subreport grows

i have a nested subreport within a main report. the upper part of the printout has around half a dozen controls and will never never take more than 4" vertically away from the landscape oriented space on it. the bottom part is allocated to the subreport. there are around half a dozen controls some of them being text and able to grow as is the subreport itself allowed to.

the vexing thing about its development comes from the fact that when the subreport 'spills over' onto a second page, the column label controls in its 'report header' do not re-appear on the second page of paper -- i know that what i'm hoping for is a solution to a non-show-stopper, however perfectionism dies hard and i just think that ms a2k oughta be able to live up to what i'm trying to get this to look like.

anybody with a clue, please get back to this.

tia.

Can't you put those controls on the page header instead of the report header? Report Header info always only shows up on the first page.

i will place them in a page header vs this report header and get back one way or another.

thx.

very welll then....

i cut the column heading labels from the report header, removed it, created a page header and pasted the labels into that.

strange results....

when i run the report, the labels don't appear to be 'there' in the nested subreport. when i run just the subreport w/o the main report, the page header labels do appear!??

does this make sense?

some more research into all this revealed that, in its infinite wisdom the group responsible for developing this failed to allow subreports to support page sections or events.

there is apparently a workaround to this little shortcoming however: by creating a new primary sorting and grouping level around a constant expression, e.g. "=1" w/o the quotations, and clicking the group header to display and setting the repeat section of this header's to 'Yes' does the trick; things begin to behave as you thought a 'page' header in a subreport would.

thanks for trying.

Interesting....are you using the .PrintCount=1 as your expression?

lwells