Others

How to Show Items Missing from Related Access Tables with an Outer Join

Tauseeq MagsiTauseeq Magsi Oct 21, 2026 868 views

Question details

The user needs to display all items and their quantities in an Access query, even if those items are missing from one or more related category tables.

How to Show Items Missing from Related Access Tables with an Outer Join
Product
Microsoft Access
Device & OS
not provided
Scenario
Creating a multi-table database query where the goal is to retain all records from a primary table regardless of incomplete related data.
Observed behavior
The current Access query returns only items that exist in every related category table, automatically filtering out records with missing relations.
Before you start

Open your Microsoft Access database and ensure you have the primary item table and all related category tables available in the Query Design view.

Solution 1Recommended

Modify Join Properties to Use an Outer Join

Adjust the relationship settings in your query to include all records from the main items table, preventing missing category data from hiding items.

By default, Access queries use an inner join, which requires a matching record in both tables. Changing this to a left or right outer join ensures the primary table's records are always displayed.

1
Open Query Design

Right-click your query in the navigation pane and select 'Design View'.

2
Access Join Properties

Locate the line connecting your main item table to a related category table. Double-click this join line to open the Join Properties dialog box.

3
Change the Join Type

Select the option that specifies: 'Include ALL records from [Item Table] and only those records from [Category Table] where the joined fields are equal'.

4
Apply to All Tables

Click 'OK'. Repeat this process for every join line connecting the main item table to other category tables, then run the query.

Modify Join Properties to Use an Outer Join
Query Results Updated: Your query will now display all items. Columns from related tables will simply show empty (null) values where data is missing.
Free Microsoft Office alternative

Manage Your Data with WPS Spreadsheet

While Microsoft Access is a specialized database tool, many data tracking, lookup, and reporting tasks can be managed easily without complex SQL databases. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office, featuring robust Spreadsheet tools that seamlessly handle xlsx formats.

  1. 1. Export Access Data: Export your current Access tables into Excel (.xlsx) format.
  2. 2. Download WPS Office: Visit the official WPS website and download the free office suite.
  3. 3. Manage Data Easily: Open your exported data in WPS Spreadsheet to utilize simple filters, lookups, and pivot tables to track your missing items.
Free and lightweight office suite for Windows, Mac, and LinuxSeamless compatibility with Microsoft Office formats like Excel (.xlsx)Familiar user interface for immediate productivity without a learning curvePowerful data analysis, VLOOKUP, and pivot table features for tracking items without complex database queries
microsoft office alternative - wps office

Frequently Asked Questions

What is the difference between an inner join and an outer join in Access?

An inner join only returns records when there is matching data in both joined tables. An outer join returns all records from one primary table, and only the matching records from the joined table, displaying null or empty values where no match exists.

Why does my Access query drop records when adding a new table?

This usually happens because Access creates an inner join by default when linking tables. If a record in your main table doesn't have a corresponding entry in the newly added table, the entire record is filtered out of the query results. Changing the relationship to an outer join fixes this.

How do I fix poor database design involving too many category tables?

Instead of creating a separate table for every category, use a many-to-many relationship structure. Create one table for Items, one table for Categories, and a junction table (e.g., ItemCategories) that stores the ItemID and CategoryID foreign keys. This prevents table bloat and simplifies query writing.