Fix Access Subform Not Displaying Records from Main Form
Question details
The user needs to resolve an issue where a database subform fails to display associated records from a linked table based on main form criteria.

- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Setting up a relational database form where a subform is supposed to populate linked assets based on the main form's contact or owner information.
- Observed behavior
- The subform remains blank or does not populate properly due to incorrect table relationships or misconfigured LinkMasterFields and LinkChildFields properties.
Before modifying your database table relationships or form properties, ensure all open forms and tables are closed, and create a backup copy of your database to prevent accidental data loss.
Configure Subform Link Properties
This is the primary fix for subforms that fail to show corresponding records. Updating the LinkMasterFields and LinkChildFields ensures the subform queries the right data based on the main form.
The Link Master Fields and Link Child Fields properties tell Microsoft Access how to connect the records in the main form to the records in the subform. If these are blank or incorrectly assigned, the subform will not filter data correctly.
Right-click your main form in the Navigation Pane on the left and select 'Design View' from the context menu.
Click once on the outer edge of the subform to select the subform control itself. Ensure the Property Sheet reflects 'Subform/Subreport' at the top, rather than the form inside it.
Open the Property Sheet by pressing F4. Navigate to the 'Data' tab. Locate 'Link Master Fields' and enter the Primary Key field name from your main form (e.g., Contacts.ID). Locate 'Link Child Fields' and enter the corresponding Foreign Key field name from your subform's table (e.g., Assets.Owner).
Save the form changes by pressing Ctrl + S. Switch to 'Form View' to verify that the subform now successfully displays records matching the main form's current record.

Correct the Table Relationships
Properly defined relationships at the database level ensure that linked fields share compatible data types, preventing forms from failing to map records.
Apply Database Naming Best Practices
Removing unsupported characters from table and field names prevents syntax errors in the background queries that populate subforms.
Looking for a Lightweight, Reliable Office Suite?
While WPS Office does not include a database management tool like Access, it serves as a robust, lightweight, and completely free alternative for your daily document productivity. If you work extensively with documents, spreadsheets, and presentations, WPS Office provides a seamless and cost-effective solution.
- 1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
- 2. Install the Software: Run the installer and follow the quick on-screen instructions to set up the suite on your computer.
- 3. Open Your Files: Launch WPS Office to instantly open, edit, and save your existing Office documents with perfect formatting preservation.

Frequently Asked Questions
Why is my Access subform completely blank?
A completely blank subform usually means the underlying table or query is returning zero records, or the subform's 'Data Entry' property is set to 'Yes' without any matching child records for the current master field. It can also happen if the user lacks permissions to view the underlying data.
What exactly are LinkMasterFields and LinkChildFields?
These are properties of the subform control that dictate how records are synchronized. 'LinkMasterFields' refers to the primary key or unique identifier on your main form, while 'LinkChildFields' refers to the foreign key in your subform's underlying table that matches the master field.
Can I link a main form and subform using text fields instead of numbers?
Yes, you can link forms using text fields, provided both fields have the exact same data type and field size. However, it is highly recommended to use numeric IDs (such as AutoNumber for the primary key and Long Integer for the foreign key) because they process much faster and are less prone to spelling or spacing errors.
Why do I get an error when enforcing referential integrity?
This error occurs if the data types of the two linked fields do not match (e.g., trying to link Short Text to a Number), or if there is already data in the child table that does not exist in the parent table. You must resolve these orphan records and ensure data types match before enforcing referential integrity.




