Data placement problem in Access report

  • Thread starter Thread starter Richard John
  • Start date Start date
R

Richard John

I'm trying to display an Access 2000 report total on the same page as the
list of numbers being totalled. But Access is not allowing me to do this,
insisting instead on displaying the total on the following page, along with
where I have a chart. This is despite there being plenty of room to
accommodate the total on the same page as the data being totalled. Both the
Total and the chart are in the Report footer section.

Can anyone help with advice or a possible solution please...

Thanks
 
I'm trying to display an Access 2000 report total on the same page as the
list of numbers being totalled. But Access is not allowing me to do this,
insisting instead on displaying the total on the following page, along with
where I have a chart. This is despite there being plenty of room to
accommodate the total on the same page as the data being totalled. Both the
Total and the chart are in the Report footer section.

Can anyone help with advice or a possible solution please...

Thanks
Click to expand...

Well, if you have placed the Total control in the Report Footer, it
will print only on the last page of the report. If the report has 3
pages it will only show on page 3, etc.

If you want to show the Total at the bottom of the page, you need to
use the Page Footer. However, you will need to change your method.

Read the Microsoft KnowledgeBase Article
132017 "How to sum a column of numbers in a report by page"
 
Thanks for your advice fredg .. :) I tried the MS/KB solution and it DID
work. However, I tried an alternative which was suggested by Ira and have
implemented that one instead.

************** SOLUTION ***************

Thanks very much Ira !!

YOUR SOLUTION WORKED!!! :) :)

This has fixed an irritating problem affecting ten reports. So there...

I just added a dummy field in the recordsource query and inserted the value
(1 in this case) to simulate the group, just as you suggested.

Interestingly enough, I was pointed to Microsoft KnowledgeBase Article
132017 which offered an alternative solution. It requires implementation
via a couple of extra controls and some code, with which I am perfectly
comfortable. I did get it to work but your solution is much easier and more
elegant... unless I'm missing something !!

Regs and thanks again ...
 
Back
Top