Categorize students based on value

[echorley]

I have a report of student's decending reading scores built from a query.

I would like a line to show up that breaks the students up between levels.

For example, there would be one line seperating the students who scored 6 and above from those who scored 4 or 5 and a line seperating those who scored 3 and below.

My report has 3 fields: SequenceID (for numbering), StudentName, DRA2_Score.

 

[benjho]

Hi,

Would groupings work (where ratings > 6 as 1 group, < 3 as anther group, and between 4 and 5 as the third group) and add a line to each group footer.

Alternatively how about using a sub report for each group with a line in the report footer.

 

[echorley]

I tried your first suggestion before I posted and the program prints multiple lines between the some of the bounds.

I am trying to stay away from sub-reports. However, it may be the only way.

 

[MSAccessRookie]

I tried your first suggestion before I posted and the program prints multiple lines between the some of the bounds.

I am trying to stay away from sub-reports. However, it may be the only way.

What about adding a fourth field to the query, and instead of displaying the results, use the field as a group sort Key. I am imagining something like:

[COLOR=red][B]GroupingField[/B][/COLOR]:IIf([COLOR=blue][B]DRA2_Score[/B][/COLOR] >=6, 1, IIf([COLOR=blue][B]DRA2_Score [/B][/COLOR]<= 3, 3, 2))

This would result in an additional Field named GroupingField that contained one of three values for any given record:

1. A value of DRA2_Score >= 6, would be Group #1
2. A value of DRA2_Score <= 3, would be Group #3
3. Any other value of DRA2_Score (4 or 5), would be Group #2

If you Group By GroupingField, and Order By DRA2_Score, the report might be able to be made to look the way you want.

 

[gemma-the-husky]

thats right

the easiest way to achieve many of these things is to get a column into the query that has suitable information - than Access just applies its standard stuff, based on the query - its much harder to handle stuff like this programmatically after the event - at the very least you end up writing loads of code

 

[echorley]

Great idea! I was focused on programming the report.