We'll we got it to work somewhat.  What we did was create a computed column in the detail using  getrow(), then tested that as "category" in the above expression.



The problem with the footer objects, was even if they were invisible and autosized, and the footer was collapsed and autosize height, it was still allocating the footer space rather than letting the detail print to the bottom of the page.



So alternately, what we need is to somehow fix the group total band to the bottom of the page like a footer.  Can we do that with a Background or some other positioning mechanism?



 

What I have done in the past is to create ANOTHER computed field "total_visible", value 0 or whatever the height of the group summary object is when visible>.

This value is set by default to 0, and is used at the expression for the HEIGHT of the group_total field.

After the values are set, issue a GroupCalc() command on the dw.



Olan

If you mean "category" to be the column of the datawindow that we are breaking the group on - then every footer of the group has the same value for the column which is the same as the last value for the group (we tried)  - What we are looking for is to have the footer only appear on the last page of the group.



Is there some other meaning for category here? Row perhaps?



 

Yes I seeee! You are right. It won't work as is.



Yes category is the grouped by column.



Maybe this would work for the visible attribute.



if ( getrow() = rowcount() or category[1] > last ( category for group 1) , 1 , 0 )



or this might work



if ( category[1] > category  , 1 , 0 )



(category[1] refers to the category of the next row )

Please see my response to Govinda below..