How to Calculate Division and State Averages Correctly in Microsoft Access
Question details
The user needs to properly aggregate and calculate division and state averages in Microsoft Access without skewing the data by averaging previously calculated employee averages.

- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Creating aggregate queries and reports to summarize scores grouped by specific parameters like division and state.
- Observed behavior
- The Access report calculates the average of already averaged employee scores, giving equal weight to each employee instead of accurate weighting based on individual score counts.
Ensure you have access to the original table containing the individual, un-averaged employee score records.
Use Aggregate Queries on Original Score Records
The most accurate way to calculate weighted averages is to aggregate the original data directly, grouped only by your desired criteria.
Averaging previously calculated averages distorts data because it assigns equal weight to groups with varying numbers of underlying records. To avoid this, calculate division and state averages directly from the base score records.
Avoid using the DAvg function for this scenario unless you are calculating domain aggregates in a specific calculated control where you can define exact criteria.
Open your Microsoft Access database, go to the 'Create' tab, click 'Query Design', and select the base table containing individual employee scores.
Double-click the specific fields you want to group by, such as 'Division' and 'State', and then add the score field you want to average.
Click the 'Totals' button in the ribbon (Sigma icon). This will add a 'Total' row to your query design grid.
Leave the Total row as 'Group By' for the Division and State fields. Change the Total row for your score field from 'Group By' to 'Average'.
Ensure you do not include employee-level identifiers, titles, or any other fields (like 'TitleR' or 'DivR') that would force the query to group at a lower, unintended level.

Try WPS Office for Your Data Analysis and Documentation Needs
While Microsoft Access handles heavy database lifting, many data aggregation and averaging tasks can be efficiently performed using spreadsheets. WPS Office provides a free, lightweight, and highly compatible alternative to the Microsoft Office suite, perfect for managing datasets, performing complex average calculations via PivotTables, and creating reports with a familiar user interface.
- 1. Import your data: Open WPS Spreadsheet and paste or import your raw dataset containing the individual score records.
- 2. Insert a PivotTable: Select your entire data range, go to the 'Insert' tab, and click 'PivotTable'.
- 3. Configure the groups: Drag the 'Division' and 'State' fields into the Rows area, and the 'Score' field into the Values area.
- 4. Change calculation to Average: Click on the Score field in the Values area, select 'Value Field Settings', and change the summary calculation from Sum to 'Average'.

Frequently Asked Questions
Why are my group averages mathematically incorrect in Microsoft Access reports?
This usually happens if the report is averaging data that has already been averaged at a lower level (like employee averages). This gives equal weight to each group instead of weighting them by the number of original records. Always aggregate directly from the un-averaged, original data records.
How do I calculate separate averages for different grouping levels?
Instead of reusing a lower-level query, create a separate aggregate query for each level. Open Query Design, add the base table, group only by the specific level you need (e.g., just State, or just Division), and set your target field's Total row to 'Average'.
When should I use the DAvg function in Access?
You should use the DAvg function only when you need to calculate a domain aggregate within a specific calculated control on a form or report, provided you can supply the correct filtering criteria. For standard grouped data, built-in query aggregation (Group By and Avg) is faster and more reliable.




