generally this is an issue with the data selection process and table joins.
Lets assume you have 1 table of students and their general demographics data, another storing their class enrollments and another table that stored their test scores and possibly another table that stores testing dates. when you join these together you only get matched records. Unless you are documenting missed tests this will start to exclude the students that had no test. You can outer join tables but this can be misleading because it will only start to include students that missed all of the tests not all weekly instances of it.
Can you write a stored procedure or a crystal command as your data source?
Is this a set date period or are you using run time parameters?
Are you crossing mutliple weeks? and/or multiple classes?
There is no simple solution to this. It really comes down to fixing how you are pulling in the data. In order to do that you have to think globally about the all of the report content. Fromt hat you try to use SQl to create the full adta set to include things that are not entered and stored as data but are inferred as existing
Edited by DBlank - 30 Mar 2015 at 4:21am
IP Logged
