21 Steps to Delete a Relationship in Microsoft Access Safely

You can safely remove a relationship in Access by backing up the file, opening the Relationships window, and identifying the precise tables and fields involved. Check and document referential integrity and cascade rules, search for dependent queries, forms, macros, and VBA, and export affected data. Delete the highlighted relationship line, then update joins, code, and macros in a copy and run tests to confirm no breakage. Continue and you’ll find step-by-step checks, fixes, and documentation tips.

Quick: How to Safely Delete a Relationship in Access

Start by opening the Relationships window in Access so you can clearly see the tables and links involved; this lets you confirm which relationship you need to remove without guessing.

Select the relationship line, verify no enforced referential integrity or cascade options will break data, right-click and choose Delete.

Then compact the database and back up before closing to prevent accidental loss.

When Should You Delete an Access Relationship?

When should you delete a relationship in Access? You should remove it when it’s obsolete, causing referential errors, or blocking necessary schema changes. Confirm no reports or queries depend on it before removing.

Reason	Visual
Obsolete link	Broken chain
Referential error	Red warning
Schema change needed	Wrench icon

Open the Right Access File and Back It Up First

Before you remove any relationship, make sure you’re working in the correct Access file and create a backup copy.

Close other databases, note the file name and path, then use File > Save As or copy the .accdb/.mdb to a safe location.

Label the backup with date/time. That way, if anything goes wrong, you can restore the original without losing data.

Identify the Exact Tables and Fields in the Relationship

Although it might seem obvious, you should confirm exactly which tables and fields make up the relationship you’re about to remove so you don’t break queries or forms that depend on them.

Open the Relationships window, hover or click the join line to view field names, note primary and foreign key fields, and list any objects (queries, forms, reports) that reference those fields before you proceed with deletion.

Check Referential Integrity and Cascade Settings

Now that you’ve identified the exact tables and fields involved, check whether referential integrity and cascade options are enabled for the relationship so you know what behavior will change when you delete it.

Before deleting a relationship, check referential integrity and cascade settings to understand resulting behavior.

You should:

Open Relationship view and select the relationship.
Inspect “Enforce Referential Integrity”.
Note “Cascade Update” and “Cascade Delete” boxes.
Record current settings before removal.

How will deleting a relationship affect the queries, forms, and reports that rely on it?

You should search Object Dependencies for affected objects, open queries to check join criteria, and inspect form/report record sources and control source expressions.

Note any broken joins or calculated fields, update SQL or design accordingly, and test each object after changes to confirm they still return correct data before removing the relationship.

Search VBA and Macros That Reference the Relationship

Check your VBA modules for code that references the relationship by table and field names so you don’t break any procedures.

Open the Macro Objects pane and inspect macros for actions that rely on the relationship.

Trace each reference you find to understand its effect before you remove the relationship.

Search VBA Modules

Wondering whether any VBA code or macros still reference the relationship you’re about to delete?

Search your modules thoroughly to avoid breaking functionality. Use these steps:

Open the VBA editor (Alt+F11) and use Find (Ctrl+F).
Search for table and relationship names, foreign keys, and join SQL.
Note matches and update code before removing the relationship.

Inspect Macro Objects

You’ve already scanned VBA modules; now do the same for Access macros and macro objects so you don’t miss references that could break when you delete the relationship. Search macro names, actions, and conditions for table or field mentions. Update or disable affected macros, then test forms and reports.

Macro Name	Action
ImportData	RunQuery
UpdateFK	SetValue
ValidateX	IfCondition
Cleanup	DeleteObject

Trace Relationship References

Before you delete the relationship, search your VBA code and macros for any references to the related tables, fields, or the relationship name so you can identify and update dependent logic; missing references will cause runtime errors in forms, reports, and automated tasks.

Use the VBA editor’s Find tool
Search modules, class modules, and form/report code
Inspect macro actions and embedded SQL
Update or document each reference before removing the relationship

Run a Dependency Check on the Tables Involved

Run a dependency check on each table involved to see which queries, forms, reports, macros, or modules rely on the relationship you plan to delete.

Use Access’s Database Tools > Object Dependencies for each table, inspect dependent objects, and note their names.

Prioritize breaking or updating dependencies before deleting the relationship to prevent runtime errors or broken UI elements.

Export or Copy Affected Table Data for Safety

Since deleting a relationship can change or remove related records, export or copy the affected tables so you can restore data if something goes wrong.

Back up only needed tables, label exports clearly, and verify the copies open correctly before proceeding.

Export tables to CSV or Access format
Save a timestamped file
Include related lookup tables
Test that exports import cleanly

Test Changes in a Copy of the Database First

When you’re ready to change relationships, work in a copy of the database so you can safely test the effects without risking live data.

Always test relationship changes on a duplicate database copy to avoid risking live data.

Duplicate the file, open the copy, and perform deletions or modifications there.

Verify queries, forms, reports, and integrity rules.

Check for orphaned records and broken references.

If everything behaves as expected, apply the same steps to the production database.

Open the Relationships Window in Access

To open the Relationships window in Access, click the Database Tools tab on the Ribbon and choose Relationships; this brings up the visual diagram where you can view, edit, or delete table relationships.

The window shows linked tables and key fields.
You can zoom and pan to inspect layout.
Use View to toggle design or SQL.
Close when done to save layout changes.

Select the Exact Relationship Line to Remove

Click the exact relationship line you want to remove so the grip points appear and the line is highlighted—this guarantees you won’t accidentally delete the wrong connection between tables. Verify the tables and cardinality shown, then proceed confidently to remove it.

Table A	Relationship	Table B
Orders	1-to-many	Customers
Products	Many-to-many	Suppliers
Invoices	One-to-one	Payments

Delete the Relationship via Right-Click Delete

Once you’ve confirmed the correct relationship line is selected, right-click it to open the context menu.

Choose Delete from the menu to remove the relationship.

You’ll be prompted to confirm, so accept to complete the deletion.

Confirm Relationship Selected

After you’ve highlighted the correct line between the two tables, make certain the relationship is the only item selected by checking for the bolded line and the small square handles at each end; this confirms you’re deleting the designated link and not a table or other object.

Verify bolded connector and square handles
Make certain no table border is highlighted
Click away if multiple items are selected
Pause to review related constraints or notes

Right‑click the bolded relationship line to open the context menu and choose Delete to remove the link; this method is quick, keeps you in the Relationships window, and prevents accidental deletion of tables since only the selected connector is affected. Confirm the prompt, and the link is gone. Use Undo if needed.

Action	Result
Right‑click	Menu opens
Delete	Link removed

Delete the Relationship via Database Tools > Relationships

Open the Relationships window from Database Tools to remove a table relationship directly.

You’ll see relationship lines connecting tables; select the line, then press Delete or right‑click to choose Delete.

Before you proceed, review linked tables and backups.

Before making changes, confirm any linked tables exist elsewhere and ensure you have recent backups.

Select the relationship line
Use Delete key or context menu
Save the changes
Verify affected queries/forms/components

Confirm Referential Integrity Constraints Were Cleared

Now that you’ve removed the relationship, verify that referential integrity constraints were cleared so related record behavior won’t still be enforced.

Open each table’s Design view, check Indexes and field properties for Lookup or Enforce Referential Integrity flags, and confirm Relationships window shows no cascade options.

Test by attempting controlled deletions or inserts in a copy of the database to ascertain constraints no longer apply.

Update or Rewrite Joins in Affected Queries

With referential integrity eliminated and behavior tests completed, check every query that referenced the deleted relationship and update or rewrite their joins to reflect the new table structure.

You’ll guarantee correct join types, preserve expected results, and prevent cartesian products.

Replace eliminated FK joins with explicit ON conditions
Use LEFT/INNER as business logic requires
Test results against sample data
Simplify complex multi-table joins

Fix Form and Report Record Sources That Break

Forms and reports that used the deleted relationship often stop returning records or throw errors, so scan their Record Source properties and update any SQL or query links that relied on the former join.

Open each form/report in design view, test its record navigation, adjust fields or rebind controls to new queries, and validate filters and sorting so users see correct data.

Update VBA Code and Macros for Removed Relationships

After deleting a relationship, check your VBA code for references to the removed fields or join logic and update them accordingly.

Also review macros for actions that rely on the relationship—modify or remove steps that no longer apply.

Finally, run tests and debug any errors to confirm forms, reports, and processes behave correctly.

Update Code References

When you remove a relationship, you’ll need to update any VBA code and macros that referenced it so your application keeps working.

Start by searching for explicit table/field names, JOINs, and Navigation or RecordSource properties that relied on the relationship.

Update references, refactor queries, and test. Use these steps:

Search project for table/field names
Update SQL JOIN clauses
Modify RecordSource/RowSource
Run unit tests and forms

Adjust Macro Actions

You’ve already updated SQL and RecordSource references; now adjust any macros that depended on the removed relationship so they keep behaving correctly. Search macros for actions referencing removed fields or joins, replace with alternative logic, and update conditions or requery targets. Document changes and version macros.

Macro Name	Action Affected	Replacement
Sales_Update	WhereCondition	Use JOIN-free filter
Report_Open	RecordSource	Use saved query

Test And Debug

Start by running the parts of your application that depended on the removed relationship and note any errors or unexpected results; this lets you quickly spot where VBA routines or macros still assume the old join or fields.

Then update code, test, and repeat:

Search VBA for references to removed fields or joins
Update SQL strings and recordsource properties
Fix macro conditions/actions
Re-run affected forms/reports and verify outputs

Recreate or Replace Relationships Safely If Needed

If a relationship proves faulty or you need a different join type, plan before you recreate or replace it so you don’t break queries, forms, or data integrity.

Identify dependent objects, note join rules and referential actions, and export or copy current relationship definitions.

Test changes in a development copy, update documentation, and implement during low-use hours so you can rollback quickly if something behaves unexpectedly.

Run Full Database Tests to Confirm No Breakages

After you’ve recreated or replaced relationships in a development copy and confirmed dependent objects, run a full suite of database tests to make sure nothing else breaks.

You should verify functionality, performance, data integrity, and security before deploying.

Run automated unit and integration tests
Execute key reports and queries manually
Validate data consistency across tables
Monitor performance under realistic load

Log the Change and Document Why You Removed It

You should log the reason you removed the relationship so others understand the decision and can reproduce it if needed.

Attach any supporting evidence—screenshots, query results, or test notes—to an archived record. This makes future troubleshooting and audits straightforward.

Record Change Rationale

Because relationships affect data integrity and future maintenance, always log why you removed one and what you changed.

You’ll make it easier to audit, restore, or explain decisions later. Include concise entries with:

who made the change and when
exact relationship names and affected tables
reason for removal and expected impact
references to related tickets or approvals

Archive Supporting Evidence

Having logged who removed the relationship and why, now archive the supporting evidence so you can prove what changed and when.

Save screenshots of the Relationships window, export schema snapshots, and attach related emails or ticket IDs.

Store files in a secure, versioned location with clear filenames and timestamps.

Note retention policy and access permissions so auditors can verify the deletion quickly.

Frequently Asked Questions

Can Deleting a Relationship Improve Performance in Large Access Databases?

Yes — deleting an unnecessary relationship can improve performance by reducing join overhead and simplifying query plans, but you shouldn’t remove enforced integrity if it risks data inconsistency; test changes on a copy first.

Will Removing Relationships Affect Linked Tables From External Data Sources?

Yes — removing relationships can affect linked external tables: you’ll lose enforced referential integrity and cascade behaviors in Access, which may change query results and updates, though the external source’s data and its own constraints remain unchanged.

How Do Relationship Deletions Interact With Access User-Level Security?

They can remove relationship entries but won’t bypass ACLs; if you’ve sufficient user-level permissions, deleting a relationship is allowed and can affect dependent objects. If you lack rights, Access will block the deletion.

Can Relationship Removal Break Data Macros or Embedded SQL in Forms?

Yes — you can break data macros or embedded SQL by removing relationships; you’ll lose referential context that macros or SQL rely on, so you should test and update affected macros, queries, and form code before deletion.

Is It Possible to Undo a Relationship Deletion Without a Backup?

No, you generally can’t undo a relationship deletion without a backup; Access doesn’t provide an automatic undo for relationship schema changes, so you’ll need to recreate it manually or restore the database from a saved copy.

Conclusion

You’ve now got a safe, repeatable process for removing relationships in Access. Back up the file, pinpoint the exact tables and fields, and verify referential integrity and cascade settings before you delete anything. Update any VBA or macros that rely on the relationship, recreate links if needed, and run thorough tests to catch hidden issues. Finally, log the change and your rationale so you—or teammates—can understand and undo it if necessary.