For this report, Do you need to see this information for all students in a single report or would it work to set it up for one student at a time?
In my experience teachers are still addicted to paper, so if we were able to make one and print it, make the next and print it, and so on I think that would serve.
Thanks for your interest.
Does that mean that a report that limits this data to that for a single student at a time is acceptable?
Yes, that would be fine.
Best guess is that you have these relationships though the names that I am using are likely different to some degree:
Students::__pkStudentID = Observations::_fkStudentID
Aspects::__pkAspectID = Observations::_fkAspectID
If we add a global field, gSelectedStudentID to Aspects, we can then click over to Relationships and use the duplicate button (two green plus signs) to make a duplicate occurrence of Observations and link it to Aspects like this:
Aspects::__pkAspectID = Observations|SelectedStudent::_fkAspectID AND
Aspects::gSelectedStudentID = Observations|SelectedStudent::_fkStudentID
You can then define a calculation field in Aspects with this expression: Count ( Observations|SelectedStudent::_fkStudentID ) to count the number of Observations linked to that Aspect for the selected student. You can clear the "do not evaluate if all referenced fields are empty" check box to get a zero when there are now such observations for a given Aspect record.
Now you can use a script to assighn the value of __pkStudentID to gSelectedStudentID and then change layouts to a list view layout that lists all the records in Aspects with the calculation field with the count function to show the total number of observations for each Aspect for the selected student.
For an explanation of the notation that I am using, see the first post of: Common Forum Relationship and Field Notations Explained