Reports: Creating, Grouping & Summaries

Reports: Creating, Grouping & Summaries

A report is the database object built for presenting information, not for entering it. Where a table stores data and a form is used to add or edit records, a report takes the output of a table or a query and formats it into a clean, structured document intended for printing, saving as PDF, or sharing electronically. Understanding what a report is for -- and how to build, group, and format one -- is the first output skill in this module.

What a Report Is For

A report presents selected information from a table or a query, arranged and formatted so it is easy to read and suitable for print or distribution. Because a report can be based on a query rather than a raw table, it can show a filtered, sorted, and calculated subset of the database -- for example, only the customers in one region, sorted alphabetically, with a running total of their orders. This is the key distinction to remember for the exam:

• A table stores the raw data.
• A query retrieves and filters the data.
• A form is used to enter, view, and edit individual records.
• A report is used to present and print/export data -- it is generally read-only by design.

Creating and Naming a Simple Report

The most direct way to build a report is to select the table or query that contains the data you want to present, then use the application's report-creation tool (in Access, the Report Wizard or the one-click Report command) to generate the report automatically. The wizard walks you through choosing which fields to include, how to sort records, and whether to group data. Once the report is generated, it must be saved and given a meaningful name -- just like a table, query, or form -- so it can be reopened, edited, or reused later. A report built directly from a table shows every record in that table; a report built from a query shows only the records and fields the query returns, which is why many real-world reports are built on top of a query rather than a raw table.

Grouped Reports and Summary Calculations

A grouped report organizes records into categories -- for example, grouping sales records by Region or grouping student records by Class -- instead of listing every record in one long, undifferentiated list. Grouping is one of the most useful report features because it lets a single report answer questions like "how many orders came from each region?" without needing a separate query for every region.

Underneath a grouping, a report can add summary calculations that are computed automatically for each group (and often for the report as a whole). The calculations you should know for the exam are:

For example, a report grouped by Sales Region could show, under each region's block of records, the sum of that region's sales, the average order value, and the count of orders placed -- all calculated automatically as the underlying data changes.

Editing a Report's Layout

Once a report exists, it is common to refine it rather than rebuild it from scratch. Editing a report typically means:

• Rearranging field and heading placement -- moving a field or its column heading to a different position in the report layout, resizing columns, or reordering which fields appear left-to-right.
• Adjusting which fields are shown or removing ones that are no longer needed.

These edits are usually made in the report's Design View (or Layout View), where fields and their labels are treated as separate objects that can be selected and moved independently.

Report Headers and Footers

Like a document, a report has dedicated header and footer areas, and the exam expects you to know how to add or modify text in them:

• The report header typically appears once, at the very start of the report -- a common place for a title, a company name, or a logo.
• The report footer typically appears once, at the very end of the report -- often used for totals or closing notes.
• Page headers/footers repeat on every printed page -- commonly used for page numbers, the date, or a running report title.

Adding or editing this text does not change the underlying data at all -- it only changes what appears on the printed or exported page, reinforcing that a report is a presentation layer sitting on top of the real data in the tables and queries.

Exam Tips

• If a question distinguishes a table/query result from a formatted, print-ready output, the answer is report.
• If a question mentions counting, totaling, or averaging values within a group, look for summary calculations as the answer, not a query calculation.
• Remember the five summary functions: sum, minimum, maximum, average, count -- and that they can be applied at the group level, not just to the whole report.
• Field/heading repositioning and header/footer text edits happen through the report's Design/Layout View, the same general approach used for editing form layouts.