@Don_Cote
To supplement what XPS35 pointed out, here is a quick overview of the essential components of a relational database application, such as those created with Access.
- The Data layer, or data tier. In a relational database ALL data is stored in tables. The design of those tables is a critical element in creating a usable application. The first step in creating a new database application, therefore, is understanding the data required and setting up tables accordingly.
- The Interface layer, or interface tier. Applications require an interface through which users can interact with the data in the tables. There are four basic types of interaction.
- Creating new records as required in one or more tables.
- Reading data back from the tables into the interface for display to users.
- Updating existing records as required in one or more tables.
- Although less frequent than adding new records, a valid application requires the ability to change, or update, existing records as appropriate.
- Deleting existing records when required.
Together, these four tasks are often referred to by their initial letters, C, R, U, and D, or "CRUD operations".
- The Logic layer, or logic tier. This is the code which automates interactions with data and manipulates the interface, as required.
Your screenshot illustrates only the 2nd of these elements, an interface in which data is retrieved from underlying tables and displayed in a formatted presentation for the viewer.
You can build a report for the interface which displays data in a manner similar to that in your screenshot. However, the storage of the data is done only in tables. And the process of adding new records, updating existing records and reading them into the report is done via an interface designed to prepare the report for display.
Investing time in understanding how relational database applications work will pay off when it's time to use the application for tasks like this one.
