I'll try to explain at leat some of those things. There are two KeepTogether properties, the one for an individual section that tries to keep each instance of the section on the same page. If the section will not fit on the remainser of the page, the entire
section will be moved to the next page. Remember this applies to each instance of the section, it does not span multiple instancees of the detail section on a group. In your report, setting the detail and group footer sections' KeepTogether tp Yes may or
may not be useful.
The other KeepTogether is for a group (in the Sorting and Grouping window) and can be set to just keep the group header and first detail on the same page or the group header all the details and group footer on the same page. For your report, the group KeepTogether
does not meet any of your stated needs.
Setting the RepeatSection [rp[erty to Yes for a group header is what you are already doing because you want the header to appear on every page. The only serious restriction with this property is that you can not use VBA code to cancel or make it invisible
on some pages. If you try, the RepeatSection property is just turned off.
The ForceNewPage property does just what it says. There are many times when the result is fine and then there are times when it is not flexible enough, such as setting it to Before Section for the group header prevents the first group from being displayed
on the same page with the report header. On the flip side, setting the group header's ForceNewPage to After Section shoves all the details to the next page. Your report would get c;oser to what you want if you set the group footer's ForceNewPage to After
Section, but this will put the report footer on a page by itself (or if there is nor report footer you'll get a blank page at the end of the report.
An alternative to ForceNewPage is to use a PageBreak control. Puttin this control at the top of a section is about the same as setting ForceNewPage to Before Section and similarly for the bottom/After Section. The advantage for the PageBreak control is
that the section can decide if it should be used or not, just by making it Visible or invisible. For your first page issue, try using a PageNreak control at the top of the group header section along with a line of VBA code in the header's Format event procedure:
Me.pgBreak.Visible = (Me.Page > 1)
I haven't use A2010 enough to know what "scissors and mallet" means.
Be more specfic about the page header section. Generally, it does what it does. It can be cacelled if that's useful.