You can create a subsummary report grouped by the date and then have two summary fields that takes the average for Wert1 and Wert2. These summary fields shouldbe placed in the subsummary part. Keep in mind that a subsummary report has to be sorted by the break field in this case the date field.
Hi Mr. Vodka,
that's what i tried today...
Create a report with summaries, define Datum and Flag as grouping criteria and Wert1 and Wert2 as data.
To get what i want, i had to hide the data and header sections, so that only the summaries were displayed.
OK, now i have a report that shows the correct values..... but.... i still can't work with the aggregated data....
I can not use the results as input for let's say graphs or further calculations.
Think about further aggregations... What is the average value of all those average values from above per week?
That's my problem.
Views are a vital part of any relational database.
If it's not possible to define views, or complex queries, it's a KO criteria for me.
"I can not use the results as input for let's say graphs or further calculations"
If the summary fields are computing sub-totals like they are in this case, use the getSummary function to access the subtotaled amount in a calculation. You also have aggregate functions that can compute totals, counts, averages etc much like a summary field. Sometimes they make a better choice than a summary field.
I've also been able to use summary fields in graphs in Filemaker 11.