Large gap between details and footer (1 Viewer)

[tmyers]

I have been fighting with this off and on for awhile, but I am finally throwing in the towel on it.

How can I get that unsightly large gap to "go away" Essentially after the Grand Total appears, I then immediately want my report footer to start. As it is right now, it gets forced to another page. I have the can grow/shrink properties set. Keep together is disabled etc.

 

[Minty]

Does it have force new page set to yes ?

And the page footer will always be at the bottom, unless there is a report footer.

 

[tmyers]

Force new page is currently set to none on both details and my group footer as well as the report footer.
Currently the only thing in the page footer is the date/time/page number.

The report footer has all the company' terms and such.

I did try removing page footer to see what it would do, but the gap remained.

 

[Minty]

Is your footer a great big single lump of text in one control or label?
If so it will nearly always start on a new page if it can't fit on the current one.

Try breaking it down into smaller chunks.

 

[onur_can]

Use page footer instead of report footer.

 

[theDBguy]

Can you post a screenshot of your report's design view? I want to see where the Grand Total, page number, date, and time are placed on the report sections.

 

[arnelgp]

there are 2 techniques (hacks) that are used on this demo.
report1 put the "grand total" to the "page footer" and make it visible
on the "last page" of the report.

report2 is more elegant.
you will notice that on "page 1" there are 26 records displayed.
so, you calculate the last page, "number of dummy lines" to produce
a total 25 (26 minus 1) lines.
then add the "grand total" (the 26th line).
it uses Union query.

 

[tmyers]

Is your footer a great big single lump of text in one control or label?
If so it will nearly always start on a new page if it can't fit on the current one.

Try breaking it down into smaller chunks.

I do have them broken out into multiple controls. Each "term" is its own control.

 

[tmyers]

Can you post a screenshot of your report's design view? I want to see where the Grand Total, page number, date, and time are placed on the report sections.

 

[tmyers]

Does that show what you were after DBGuy?

 

[Minty]

Is your clarification section (it's slighty unusual to have a sub report in a report footer) set to can shrink/can grow YES, and if it is, make it really small - literally 1 pixel high.

It will grow to accommodate any data if present.

 

[tmyers]

Is your clarification section (it's slighty unusual to have a sub report in a report footer) set to can shrink/can grow YES, and if it is, make it really small - literally 1 pixel high.

It will grow to accommodate any data if present.

Didn't think of that. I just changed that but for the record, the gap remains.
That sub-report just contains chosen clarifications that are specific to the particular job being quoted. So not every job is the same. Some need the clarifications/extra terms.

 

[AccessBlaster]

Recreate the report using the report wizard, answer all the prompts. After the report has finished tweak it in design view. Sometimes the wizard adds functionality that's not obvious.

 

[tmyers]

Recreate the report using the report wizard, answer all the prompts. After the report has finished tweak it in design view. Sometimes the wizard adds functionality that's not obvious.

The report was initially made via the wizard. I added the sub-report and some other controls however as well as the grouping to give me the Grand Total.

 

[theDBguy]

Does that show what you were after DBGuy?

Hi. Yes, it does. However, re-reading your original post,

Essentially after the Grand Total appears, I then immediately want my report footer to start. As it is right now, it gets forced to another page.

I think the report footer being a subform may have something to do with it.

So, just as a test, could you replace the report footer with a simple text to see if it goes up or still show up in a new page?

Just a thought...

 

[tmyers]

Hi. Yes, it does. However, re-reading your original post,

I think the report footer being a subform may have something to do with it.

So, just as a test, could you replace the report footer with a simple text to see if it goes up or still show up in a new page?

Just a thought...

I just quickly tried this.
I deleted out the sub-report and only left my labels with their text in. Same result. All of it was forced to a new page after the total. I also did a quick test and removed the page footer. No change there either.

 

[tmyers]

there are 2 techniques (hacks) that are used on this demo.
report1 put the "grand total" to the "page footer" and make it visible
on the "last page" of the report.

report2 is more elegant.
you will notice that on "page 1" there are 26 records displayed.
so, you calculate the last page, "number of dummy lines" to produce
a total 25 (26 minus 1) lines.
then add the "grand total" (the 26th line).
it uses Union query.

@arnelgp I had completely forgotten that I downloaded your sample. How did you get that grand total in rpt2? I tried forever to figure that out to no avail.

Edit:
Found it in the on load and am looking at that now. It seems much more elegant then the grouping method I am using.

 

[theDBguy]

I just quickly tried this.
I deleted out the sub-report and only left my labels with their text in. Same result. All of it was forced to a new page after the total. I also did a quick test and removed the page footer. No change there either.

Sounds like there may be either a page break or a force a new page setting in there somewhere. If you can post a sample copy of the report, we could try to take a look for you.

 

[tmyers]

Sounds like there may be either a page break or a force a new page setting in there somewhere. If you can post a sample copy of the report, we could try to take a look for you.

Sure thing! I am retweaking to implement the grand total code provided by arnelgp in their example then I should be able to.

 

[tmyers]

In tinkering around, apparently it was the auto resize property on the report itself. I checked that to no and magically everything "smooshed" together how I was after.

Weird that that property would cause that to happen. Doesn't seem like it should.