I find that I am puzzled by your example. A summary report would be expected to sum data and I do not see why a value of 3:20 for student 1 produced by summing 1:15 and 2:05 is incorrect as this would indicate that the student's total session time was 3:20.
What value would be the correct value and why?
That is not the problem. It is the quota field.
I want to get a sum of their quotas, both daily and weekly. For the daily quota, instead of giving me 20 for the quota field above, it gives me 25 because there are 2 instances of student 1 in the sessions table, instead of 20.
For the weekly, it gives me 60, instead of 45, again because student 1 has 2 entries, to it adds the quota twice, instead of just once per student, even though there may be multiple session entries.
What is your summary field summarizing? I can see how that would double the quota if the student has two sessions and triple it if they had three. But getting 25 instead of 20 because a student has two sessions doesn't make sense. Won't that student have the same quota specified for each session?
I would think that for a given student, the quota would be the same for each session and that you would be comparing the sum of all the student's sessions to their specified quota. In such case, you would simply need to include the original quota field from the student table on the layout and not use a summary field.
Let me better explain. I am trying to summarize the daily quota per STUDENT not per SESSION record.
TABLE 1: students
TABLE 2: sessions
Table 1 contains:
Daily expected Quota
When running the report on number of sessions, I want to get (summarized):
studentName (relatedData) DailyQuote (related Data) sessionLength (summarized)
At the end, there is a trailing grand summary:
Total Daily Quota, Total Sessions Length
The daily quota shouldn't be added over and over per each session instance of the same student. It should be summed ONCE per student, no matter the number of sessions that occur. That is what I am trying to achieve.