How to Keep Related Access Tables Synchronized in a One-to-One Relationship
Question details
The user wants to automatically synchronize or create a matching child record when a new record is added to a parent table in Microsoft Access, specifically within a one-to-one relationship.

- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Managing database records where a parent table and a child table share a one-to-one relationship linked by a primary and foreign key (e.g., EmployeeID).
- Observed behavior
- Microsoft Access does not automatically generate a corresponding child record when a new parent record is created.
Before attempting to automate record creation, review your database design to ensure a one-to-one relationship is truly necessary, as these are typically reserved for modeling subtype data rather than standard relational tables.
Use a Parent Form and Related Subform Linked by Keys
The best practice in Microsoft Access is to use the user interface to manage data entry manually when needed, rather than forcing automatic record creation in the backend.
A one-to-one relationship is appropriate when one table represents a subtype of the entity represented by the other table. In this design, do not automatically create duplicate rows unless the data model strictly requires them.
Open your Microsoft Access database, navigate to the 'Create' tab on the ribbon, and create a main form based on your primary (parent) table.
Use the Form Design tools to insert a 'Subform/Subreport' control into your main form, basing this subform on your related (child/subtype) table.
Select the subform control, open the Property Sheet, and under the Data tab, ensure 'Link Master Fields' and 'Link Child Fields' are set to your linking identifier (e.g., EmployeeID).
Use this form interface for data entry. The child record will now only be created when you actively enter specific subtype data into the subform fields.

Review Table Normalization and Merge Tables
If you find that every single parent record must have a perfectly synchronized child record with no exceptions, your tables are likely not normalized properly.
Automate Record Creation Using Data Macros
While generally discouraged due to the risk of creating empty records, you can force child record creation using an After Insert data macro.
Looking for a Free Alternative for Your Daily Office Tasks?
While Microsoft Access is designed for relational database management, your everyday document, spreadsheet, and presentation needs require a streamlined, efficient solution. WPS Office offers a highly compatible, completely free alternative to Microsoft Office.
- 1. Download the installer: Visit the official WPS Office website to download the free installer for your operating system.
- 2. Install the suite: Run the downloaded file and follow the straightforward on-screen instructions to set up WPS Office.
- 3. Start working: Launch WPS Office to instantly open, edit, and save your existing Office files with perfect formatting retention.

Frequently Asked Questions
Why doesn't Microsoft Access create one-to-one related records automatically?
Access avoids automatically generating duplicate or empty rows in a related table to save database space and maintain strict relational data integrity. Record creation must be explicitly driven by data entry or business logic.
When is it appropriate to use a one-to-one relationship in Access?
One-to-one relationships are best suited for modeling subtype hierarchies. For example, a general 'Employees' table might link one-to-one with a 'SalariedEmployees' table, where the subtype table only holds data applicable to salaried staff.
How do referential integrity rules affect one-to-one relationships?
Referential integrity ensures that every child record corresponds to a valid parent record and prevents orphaned records. However, it does not force the creation of a child record when a parent is created.
Can I force users to enter data into the related one-to-one table?
Yes, you can mandate data entry by implementing form-level validation using VBA or macros before the parent record is saved, ensuring both the main form and subform fields are completed.




