Lesson 2	What is a form?
Objective	Describe the uses of an Access form.

What Is an Access Form?

In Microsoft Access (including Access 365), a form is a database object used to create a user interface for working with data stored in tables (often through queries). A form does not replace tables; it sits on top of them to make data entry, review, and navigation faster and less error-prone. ^[1]

Primary Uses of Forms in Access

Data entry and editing
Forms provide a clean layout (labels, grouping, tab order) that helps users enter and edit records without scrolling through dozens of table columns.
Guided navigation
Forms can include buttons and menus (Next/Previous record, Find, Filter, Open related form) so users can move through the application without touching raw tables.
Validation and data quality controls
You can enforce rules through control properties (Required fields, input masks, default values) and through macros or VBA events (Before Update, After Update) to prevent bad data from being saved.
Working with related data
Forms are ideal for displaying a “main record” plus its related records (for example, a Project with many time entries) by using subforms and master/child linking fields.
Application workflow and automation
Forms can trigger actions (run a query, export to PDF, send an email, open a report) using command buttons, macros, or VBA.

Bound vs. Unbound Forms

Bound forms connect directly to a table or query. Users can add, edit, and delete records in the underlying data source.
Unbound forms are not tied to a single record source. They are commonly used as switchboards, search screens, parameter entry screens, or dashboards that launch other objects.

How Forms Fit into the Typical Access Workflow

Access applications are commonly built and used in a logical sequence: Tables store the data, Queries shape the data, Forms provide the user interface, and Reports produce formatted output.

Forms are a practical supplement to tables: tables are optimized for storage, not for user experience. When records have many fields (or long values), forms present the same information in a cleaner layout and can reduce errors with validation and controlled input.

Forms are the third object in the typical logical flow: — **Forms in context:** Forms are typically used after tables and queries are in place.

**Tables** hold the data.

**Queries** filter, calculate, or join the data.

**Forms** provide a user-friendly screen for entering and viewing data.

**Reports** format data for printing or distribution.

Microsoft Access - [Projects] — **Example:** A simple form for entering and reviewing project data

Project ID: 1

Client: Network Consultants, Inc.

Project Description: General Marketing Brochure

Start Date: 6/1/2024

Due Date: 6/21/2024

Completed:

Paid:

**What this form demonstrates**

A clean screen for reviewing a single record (the Project).

A structured layout that is easier to read than a wide table.

Controls (checkboxes, text fields) that guide user input.

**Related table data (example fields)**

HoursID

Date

Hours worked

**Table records (sample)**
`1 | 6/1/2024 | 4 2 | 6/3/2024 | 4 3 | 6/6/2024 | 2`

Record navigation typically appears at the bottom of a bound form (example: *Record: 1 of 22*).

In the next lesson, you will create an AutoForm from one table.

[1]database object: In Microsoft Access, a form is a database object that can be bound to a table or query (or left unbound). When bound, the form provides a structured UI so users can view, add, edit, and delete records in the underlying data source.