Grouping page break not working

[Maverick]

I have a report that has 3 groups created. The 1st is by project, the 2nd is
by task, and the 3rd is by start date. I am trying to make it so that the
page breaks for each date (i.e. tasks for 9/9/09 is on one page, 9/10/09 is
on another).

I have tried using the Keep Together function of the group as well as Force
New Page for the group header and footer.

Nothing seems to work. The only out of the ordinary thing is that I have a
subreport in the detail section. However, I've tried moving it to the group
footer for the date group and that doesn't change anything.

This is driving me crazy. I have scoured the forum and found nothing that
helps. Thanks for any advice.
--

HTH

Don''''t forget to rate the post if it was helpful!

Please reply to newsgroup only, so that others may benefit as well.

 

[BruceM]

Are you saying you have start dates per task, and that for each task you
want the dates separated by page?

 

[Keith Wilby]

that is what exactly the OP stated.

This statement only goes to prove that you know nothing of requirements
gathering. If there is an element of doubt in a developer's mind as to what
a particular requirement is then it is better to have the client re-state it
rather than make an assumption and supply something that is wrong. It's one
of the most fundamental steps in the requirement gathering process. Your
statement makes you look foolish and inexperienced.

 

[Maverick]

Each task does have a date. What I want is to have all the tasks grouped
first by project, then by task, then by date. For examle, all tasks in
Project 1 show under Project 1 and those under Project 2 show under Project
2. Within Project 1, I want the tasks to show that belong to that project.
Ultimately, I want these tasks to be grouped by date so that all of the tasks
on 9/8 show under that date and those on 9/9 show on that date. Then, I want
the report to break after the dates so that all of the 9/8 tasks show on one
page and those for 9/9 show on another.

I've done a work around for this that works okay. It's not as sophisticated
as what I was trying for, so a solution to this would still be useful.

Thanks.

--

HTH

Don''''t forget to rate the post if it was helpful!

Please reply to newsgroup only, so that others may benefit as well.