D
Dave Lee
My third try at posting this - sure hope that all of them don't show up all of a sudden
I am a novice ACCESS user and am running into enough report grouping surprises to lead me to think that I have some fundamental misunderstanding here. The part of the application that I am currently working on is to build a golf scorecard as a report. The report is grouped on "Tee Time" and then "Holes". All golfers with the same Tee Time go onto the same scorecard. And then the holes for the selected course are printed along with player specific handicap information and room for score reporting by the players. There is one page per scorecard
The report has a Group Header associated with Tee Time where the relevant course/player information lives. There is a second Grouping on Holes where the hole information is printed. The Holes are grouped every 9 holes (front nine and back nine) with a group Footer for each nine holes. Tee Times and Holes are sorted Ascending.
All this works well with two exceptions
1) I had to specify a Group Interval on Holes of 10 rather than 9, but 10 works. It just surprised me that I had to do it that way. The Group Footer counts as one maybe
2) The Holes come out in the proper Groups (first 9 all together and the second nine all together), but they come out in random order - 9-8-6-4-8-2-1-5 instead of 1-2-3-4-5-6-7-8-9. One comes out as 1-2-3-4-9-5-6-7-8 which is close enough to "correct" to make me think that this isn't random. But I can't find a pattern here
Am I miss-using grouping here? This seems like the perfect application of grouping, but the darn holes just won't sort. The relevant paramters are
Tee Time
Ascending sor
Group Header Ye
Group Footer N
Group on Each Valu
Group Interval
Keep Together Whole Grou
Hole
Ascending Sor
Group Header N
Group Footer ye
Group On Interval
Group Interval 10
Keep Together Whole Grou
From the report Properties page the Grp Keep Together is Per Pag
Is this a misapplication of report grouping? It seems like a perfect fit, but the darn holes just will not sort. FWIW, the query that this report is bound to does create all records in the proper order.
Thanks
dave
I am a novice ACCESS user and am running into enough report grouping surprises to lead me to think that I have some fundamental misunderstanding here. The part of the application that I am currently working on is to build a golf scorecard as a report. The report is grouped on "Tee Time" and then "Holes". All golfers with the same Tee Time go onto the same scorecard. And then the holes for the selected course are printed along with player specific handicap information and room for score reporting by the players. There is one page per scorecard
The report has a Group Header associated with Tee Time where the relevant course/player information lives. There is a second Grouping on Holes where the hole information is printed. The Holes are grouped every 9 holes (front nine and back nine) with a group Footer for each nine holes. Tee Times and Holes are sorted Ascending.
All this works well with two exceptions
1) I had to specify a Group Interval on Holes of 10 rather than 9, but 10 works. It just surprised me that I had to do it that way. The Group Footer counts as one maybe
2) The Holes come out in the proper Groups (first 9 all together and the second nine all together), but they come out in random order - 9-8-6-4-8-2-1-5 instead of 1-2-3-4-5-6-7-8-9. One comes out as 1-2-3-4-9-5-6-7-8 which is close enough to "correct" to make me think that this isn't random. But I can't find a pattern here
Am I miss-using grouping here? This seems like the perfect application of grouping, but the darn holes just won't sort. The relevant paramters are
Tee Time
Ascending sor
Group Header Ye
Group Footer N
Group on Each Valu
Group Interval
Keep Together Whole Grou
Hole
Ascending Sor
Group Header N
Group Footer ye
Group On Interval
Group Interval 10
Keep Together Whole Grou
From the report Properties page the Grp Keep Together is Per Pag
Is this a misapplication of report grouping? It seems like a perfect fit, but the darn holes just will not sort. FWIW, the query that this report is bound to does create all records in the proper order.
Thanks
dave