Yet another “blank page†issue

[terri]

I have a report with a grouping that may optionally be set to page break on
change. When I change the Group Footer’s ForceNew property from 0 to 2 in
the Open Event to get the page break, I always get a blank page at the end of
the report.

I thought this would be easy… what am I missing?

 

[Marshall Barton]

I have a report with a grouping that may optionally be set to page break on
change. When I change the Group Footer’s ForceNew property from 0 to 2 in
the Open Event to get the page break, I always get a blank page at the end of
the report.

Group footers are not smart enough to know when they are at
the end of the report.

Try setting the group header section's ForceNewPage to 1

 

[terri]

Thanks for the reply Marsh.

Unfortunately, that just moved the blank page to the front.

I'm using 2000RT – do I chalk this up to another issue with the runtime ?

 

[Marshall Barton]

Thanks for the reply Marsh.

Unfortunately, that just moved the blank page to the front.

I'm using 2000RT – do I chalk this up to another issue with the runtime ?

I never used A2K so I don't know for sure, but I suspect
that the blank page is the report header. Try removing the
report header, making it invisible or setting its Height to
0

 

[terri]

You’re right that it’s another section causing the problem -- although I’m
not using either the Report or Page Header…

A while back you responded to a post of mine regarding the RepeatSection
property; it turned out that the property cannot be changed at runtime and
changing the visible property of a section at runtime causes the 2000RT to
hang. To work around this, I use three groups to build a custom page header.
If I take these groups out of play the data group header does indeed print
on the first page. Put them in and the data group starts on page two. (Keep
with first detail doesn’t have any effect.)

So the group footer is never smart enough to know it’s on the last page, and
the group header is only smart enough to know it’s on the first page if it’s
the first group… any other options or am I pretty much out of luck again?

 

[Marshall Barton]

You’re right that it’s another section causing the problem -- although I’m
not using either the Report or Page Header…

A while back you responded to a post of mine regarding the RepeatSection
property; it turned out that the property cannot be changed at runtime and
changing the visible property of a section at runtime causes the 2000RT to
hang. To work around this, I use three groups to build a custom page header.
If I take these groups out of play the data group header does indeed print
on the first page. Put them in and the data group starts on page two. (Keep
with first detail doesn’t have any effect.)

So the group footer is never smart enough to know it’s on the last page, and
the group header is only smart enough to know it’s on the first page if it’s
the first group… any other options or am I pretty much out of luck again?

I guess that rules out the use of ForceNewPage ;-)

You can revert back to the old reliable technique of putting
a page break control (named pgNewPage) at the top of the
group header and making it visible the second time the group
is displayed. Use a running sum text box (named txtRunGroup
and expression =1) in the group header to determine the
first time you are processing the group:
Me.pgNewPage.Visible = txtRunGroupCount > 1

 

[terri]

Thanks Marsh – that did it!

I was all set for the runtime to hang at the format event again, but this
works just fine.

I’d never used a page break control before – interesting that “visibleâ€
isn’t in the property sheet...

 

[Marshall Barton]

Thanks Marsh – that did it!

I was all set for the runtime to hang at the format event again, but this
works just fine.

I’d never used a page break control before – interesting that “visible”
isn’t in the property sheet...

I don't find it interesting. Seems more like an oversight
to me. But it has been that way forever, so maybe there's a
secret reason??