Inspection Database- Template or Example

Patrick Snyder 5 Reputation points
2026-03-13T19:15:34.97+00:00

Hello,

I am trying to create a new database for an dimensional inspection report. See snippet below. Before I waste a bunch of my time creating tables, forms and such, I want to know the best way (and easiest) to do this. The snippet only represents the first four inspection points or features. Currently, I use a form that I created in Excel and it works well but I much rather start using Access so that I can view multiple inspection reports without having to search through many different folders.

User's image

So my vision of the form would look like the following: The header (not shown in snippet above) would have a part number and a report number that I would provide (unable to use the autonumbering feature), plus there would be some other key header details, date and such. Each different part (or report) that is inspected would have a different number of features requiring to be inspected. Example: inspecting cube, there is a width, length and height. This means there would be a total of three features, for each sample, requiring to be inspected. If I had five samples, that is a total of 15 different measurements.

The number of features are listed down in column B "Item". Key information about the dimension being inspected are columns C thru Q (column C through I is a merged cell). Each inspection requires, at minimum 5 samples to be inspected, this is columns R thru V. Columns R thru V is the as-found condition.

  • Merged Column C thru I- value that I enter.
  • Column J- value that I enter.
  • Column K- value that I enter.
  • Columns L, M, and N would be values that I need to enter.
  • Columns O, P and Q are fields that are auto-calculated based on Columns L, M, and N.
  • Columns R thru V are values that I enter but with conditional formatting change cell color is the as-found measurement is in tolerance based on values in Columns O, P, and Q.

The form should be able to support a minimum of 300 different features but ideally it should be infinite.

Any help to get me started would be much appreciated. I've done some searching for something similar but I am unable to find anything and I am sure the AI answer will not be much help either!

Thanks,

Microsoft 365 and Office | Access | Other | Windows
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-03-13T19:16:12.7133333+00:00

    Access does not have a built‑in “inspection database” template that matches this layout exactly, but it can handle this scenario well if the data is normalized and the form is designed on top of that structure.

    A simple starting design that supports any number of features and measurements per part/report:

    1. Reports (header information)
      Stores one row per inspection report.
      • ReportID (AutoNumber, primary key – internal only)
      • ReportNumber (Text – the manual report number entered)
      • PartNumber (Text)
      • DateInspected (Date/Time)
      • Other header fields as needed (customer, inspector, etc.)
    2. Features (what is being measured)
      Stores one row per feature on a report (width, length, height, etc.).
      • FeatureID (AutoNumber, primary key)
      • ReportID (Number, Long Integer – foreign key to Reports.ReportID)
      • ItemNumber (Long – corresponds to column B “Item”)
      • NominalDescription (Text – what is now in merged C–I)
      • InspectionMethod (Text – column J)
      • UnitOfMeasure (Text – column K)
      • Nominal (Number – column L or K depending on how defined)
      • MinusTol (Number – column M)
      • PlusTol (Number – column N)
      • LSL (Number – column O, can be calculated)
      • USL (Number – column P, can be calculated)
      • TotalTol (Number – column Q, can be calculated)
      LSL/USL/TotalTol can either be stored or calculated in queries/forms as:
      • LSL = Nominal − MinusTol
      • USL = Nominal + PlusTol
      • TotalTol = PlusTol + MinusTol
    3. Measurements (as‑found values)
      Stores one row per actual measurement.
      • MeasurementID (AutoNumber, primary key)
      • FeatureID (Number, Long Integer – foreign key to Features.FeatureID)
      • SampleNumber (Integer – 1,2,3,4,5, …)
      • MeasuredValue (Number)
      This structure supports any number of samples (not just 5) and any number of features per report.
    4. Forms a. Report form (single‑form)
      • Record source: Reports table.
      • Shows header fields (ReportNumber, PartNumber, Date, etc.).
      b. Features subform (continuous form)
      • Record source: Features table.
      • Linked to Report form by ReportID.
      • Layout columns to match the Excel header: ItemNumber, NominalDescription, InspectionMethod, UnitOfMeasure, Nominal, MinusTol, PlusTol, LSL, USL, TotalTol.
      • Use calculated controls for LSL/USL/TotalTol if preferred instead of storing them.
      c. Measurements subform (continuous or datasheet)
      • Record source: Measurements table.
      • Linked to Features subform by FeatureID.
      • Shows SampleNumber and MeasuredValue.
      To mimic the Excel layout of 5 fixed columns (1–5), use:
      • A crosstab query or a form with 5 bound controls (Sample1–Sample5) that read/write to the Measurements table via VBA.
        Or keep it simple and show measurements vertically (one row per sample) in a datasheet subform.
    5. Conditional formatting (in‑tolerance highlighting) On the Measurements subform, add conditional formatting to the MeasuredValue control:
      • Condition 1: Field Value Is Less Than [LSL] → set background color (e.g., red).
      • Condition 2: Field Value Is Greater Than [USL] → same color.
      • Otherwise leave normal.
      LSL and USL can be exposed on the subform via the relationship to Features (include them in the subform’s record source or reference them from the parent form).
    6. Getting started quickly in Access
      • Create a Blank desktop database.
      • Create the three tables above and define relationships: Reports 1‑to‑many Features, Features 1‑to‑many Measurements.
      • Use the Form Wizard to build the main Report form with a Features subform; then add the Measurements subform.
      • Use queries to calculate LSL/USL/TotalTol if not stored.
      Access templates and wizards can help with the basic database and form creation, but this inspection layout requires a custom design as outlined.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. George Hepworth 23,120 Reputation points Volunteer Moderator
    2026-03-13T19:27:06.1166667+00:00

    Database development begins with tables. Do nothing with regard to forms for display until your tables are properly designed and built. This can't be emphasized too much. Without properly normalized tables, your forms and reports will be crippled.

    There are hundreds of good and excellent discussions of Database Normalization available if you search for that term. Look for Database Normalization, to distinguish it from other uses of Normalization.

    Identify the data you need to track and store, then use what you learn about Database Normalization to set up some tables. We'll help you work from there to a properly normalized table design, at which point it will become worthwhile to discuss forms.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.