Lesson 1

Reports are one of Microsoft Access’s strongest features because they turn relational data into a polished, shareable deliverable. In a modern Office / Microsoft 365 environment, Access reports are still highly relevant when you need a structured output that is:

• Formatted (headers/footers, page numbers, labels, totals, sections)
• Grouped and summarized (subtotals, grand totals, counts, averages)
• Repeatable (the same layout every run for auditing or operations)
• Exportable (PDF for distribution, printing, or archiving)

A report is not simply “a pretty table.” It is a presentation layer that sits on top of a query (or multiple queries), designed to communicate results to stakeholders who may not use Access directly.

Use a report when your primary goal is presentation rather than interactive analysis. Typical scenarios include:

Operational and management reporting

Weekly sales summaries, monthly billing statements, compliance checklists, inventory snapshots, exception reports, and executive rollups.

Standardized outputs

Reports that must look the same each time—especially when they are reviewed by managers, auditors, or clients.

Printing and PDF workflows

Access reports are optimized for page layouts: margins, page breaks, headers, footers, and multi-page formatting are first-class features.

Grouping, sorting, and totals

If you need subtotals by department, totals by customer, or summary sections by region, reports are the right tool.

Reports based on parameterized queries

You can drive reports from form inputs (date ranges, customer selection, status flags) to create “run it when needed” reporting workflows.

There are cases where Access reports are not the best fit:

1. Enterprise-scale analytics: If the dataset is extremely large or requires distributed compute, use a database platform plus Power BI or other BI tooling.
2. Real-time dashboards: Access reports are not designed for continuous refresh dashboards; they are designed for “run, render, and share.”
3. Highly interactive exploration: If users need ad hoc slicing, drill-through, and self-service modeling, Power BI (or Excel Power Pivot) is typically better.

In many organizations, Access remains a practical solution for departmental apps and line-of-business workflows. A common modern pattern is:

1. Store data in Access tables for small systems, or link Access to SQL Server/Azure SQL for shared multi-user systems.
2. Shape the dataset with queries (including joins, filters, calculated fields, and parameters).
3. Build forms for user-driven data entry and report selection criteria.
4. Publish reports to PDF for distribution via email, SharePoint/Teams file storage, or an internal portal.

This approach keeps Access focused on what it excels at: rapid application development, structured data entry, and consistent reporting output.

Reports give you a professional way to present your data. In this module you will learn how to design, generate, and refine reports so they can be used in day-to-day operations and shared with others.

1. Describe when to use a report (and when to choose another reporting tool)
2. Create a report using the Report Wizard and built-in layout options
3. Navigate Report View, Layout View, and Print Preview
4. Create mailing labels using label/report layouts
5. Edit and add controls in Report Design view
6. Use report sections (Report Header/Footer, Page Header/Footer, Group Header/Footer, Detail)
7. Create calculated controls (totals, expressions, conditional formatting)
8. Add page breaks and control pagination for clean printed/PDF output

While the Report Wizard can generate a strong starting point, real-world reporting often requires manual design. Manual design is where you control layout, grouping levels, formatting, and how the report behaves when printed or exported.
Reports commonly include multiple “layers” of information: summaries at the top, detail rows in the middle, and totals or footnotes at the bottom. When the report needs to present related information that does not fit cleanly into one dataset, Access provides a powerful solution:
subreports.
Subreports let you embed one report inside another. This is useful when a main report has a parent context (for example, one customer per page), and the embedded subreport shows related child rows (orders, payments, line items, service calls).

A typical workflow for building a professional report manually looks like this:

1. Define the query that supplies the report’s recordsource (or multiple queries for main/subreport scenarios).
2. Create the shell report in Design View (sections, titles, margins, and page setup).
3. Add grouping and sorting (for example, group by customer, then by order date).
4. Add calculated controls (subtotals, totals, expressions) and apply formatting rules.
5. Embed subreports when you need parent/child reporting on the same page.
6. Validate output in Print Preview and export to PDF to confirm pagination, spacing, and readability.

Forms and reports together give Access its “application platform” feel: forms capture and validate inputs, while reports deliver consistent, professional outputs for decision-making and documentation.