Report footer totals print on 2nd page

[Guest]

I'm trying to create a timecard that has totals for various groups (reg hrs,
vac hrs, etc) at the bottom of the page. It works fine if I leave the report
as a single column. But I've made two columes - one for each of two weeks.
Now the summary, which is in the report footer, prints on the next page. If
I try to put the summary in the page footer, I get the #error message. Can
anyone tell me why the page footer and report footers treat the same
calculation differently?
Thanks,
Walt

 

[Marshall Barton]

I'm trying to create a timecard that has totals for various groups (reg hrs,
vac hrs, etc) at the bottom of the page. It works fine if I leave the report
as a single column. But I've made two columes - one for each of two weeks.
Now the summary, which is in the report footer, prints on the next page. If
I try to put the summary in the page footer, I get the #error message. Can
anyone tell me why the page footer and report footers treat the same
calculation differently?

Unless you specify otherwise, the report footer appears
immediately after the last detail record. Check to make
sure each section's ForceNewPage property is not set.

Another issue is if you have your columns set to Down then
Across snaking, the first column will fill the page before
the second column starts. It doesn't sound like this is
your issue, but it does affect where the report footer
appears.

Regardless, the report footer does not appear at the bottom
of the last page. To get that you need to use the Page
footer. However, the aggregate functions only operate on a
a group or the entire report, not on a page basis. On way
to over come this is to make the report footer invisible and
have the page footer text boxes use expressions that refer
to the report footer calculated text boxes.

 

[Guest]

Thank you Marsh.
Actually, I do believe that my column formating is the problem because I
have it set at 'down snake across'. I tried your suggestion of referencing
the report footer calculated boxes, and it looks like that is going to work
just fine. Just out of curiosity, is there any way to stop the 1st column
from going all the way to the bottom of the page? Can I fool the system into
thinking that the page is only 9" tall instead of 11". I don't know if that
would be another way to accomplish what I needed anyway.
Thanks again.
Walt

 

[Marshall Barton]

No, you can't fool with the page size.

If you use Sorting and Grouping on the week, you could set
the group header section's NewRowOrCol property to
BeforeSection to get the second week to start a new column.
Make the header section very small if you don't have
anything to display in it.

 

[Guest]

Your first suggestion has worked out just fine. I'll take a look at the
second one to see what the result is.
I do have one additional question. This timecard spans a two week period.
At the end of each group (week) I have the total hours for that week. But I
don't know how to grab each week's total as a unique number and manipulate it
(primary interest is to calculate the Overtime seperately for each week).

No, you can't fool with the page size.

If you use Sorting and Grouping on the week, you could set
the group header section's NewRowOrCol property to
BeforeSection to get the second week to start a new column.
Make the header section very small if you don't have
anything to display in it.
--
Marsh
MVP [MS Access]

Actually, I do believe that my column formating is the problem because I
have it set at 'down snake across'. I tried your suggestion of referencing
the report footer calculated boxes, and it looks like that is going to work
just fine. Just out of curiosity, is there any way to stop the 1st column
from going all the way to the bottom of the page? Can I fool the system into
thinking that the page is only 9" tall instead of 11". I don't know if that
would be another way to accomplish what I needed anyway.

 

[Marshall Barton]

You might be able to get that by using the group footer
section to do the calculations. Generally, one or more text
boxes with an expression using the Sum function is all you
need.

 

[Guest]

Thank you for the additional info. Actually (surprise) I figured it out, and
this report is looking very much like I want it to. I'm quite satisfied
with it. Thank you for all of your help.

You might be able to get that by using the group footer
section to do the calculations. Generally, one or more text
boxes with an expression using the Sum function is all you
need.
--
Marsh
MVP [MS Access]

Your first suggestion has worked out just fine. I'll take a look at the
second one to see what the result is.
I do have one additional question. This timecard spans a two week period.
At the end of each group (week) I have the total hours for that week. But I
don't know how to grab each week's total as a unique number and manipulate it
(primary interest is to calculate the Overtime seperately for each week).