Others

Fix #Deleted Records Error in Access ODBC Linked Tables

Bushra ParveenBushra Parveen Oct 28, 2026 869 views

Question details

Users are encountering a #Deleted error in all fields of records linked to a SQL Server database via ODBC in Microsoft Access, often occurring after an Office update.

How to Fix #Deleted Records in Access Through ODBC
Product
Microsoft Access
Device & OS
not provided
Scenario
Viewing or querying data from SQL Server linked tables in Microsoft Access where a text field is used as the primary key.
Observed behavior
Access displays '#Deleted' for all linked records and fields instead of showing the actual database values.
Before you start

Before attempting to roll back Office versions or alter database schemas, completely back up your Access database and ensure you have administrative permissions on your device.

Solution 1Recommended

Roll Back Microsoft Office to a Known Working Build

If the #Deleted error began immediately after an automatic Office update (such as version 2205), reverting to the previous build is the most reliable workaround.

Microsoft Access sometimes introduces compatibility issues with ODBC drivers during routine updates. Using the Office Deployment Tool (ODT) allows you to revert your installation to a previously stable version until an official patch is released.

1
Download the Office Deployment Tool

Download the official Office Deployment Tool from the Microsoft website and extract the files to a local folder.

2
Create a Configuration File

Create an XML configuration file specifying the exact earlier version number of Office that you wish to roll back to.

3
Run Setup as Administrator

Open Command Prompt as an administrator, navigate to the extracted folder, and run the setup command targeting your new configuration file.

4
Trigger the Office Update

Open Microsoft Access, navigate to File > Account > Update Options, and click 'Update Now' to apply the rollback.

Roll Back Microsoft Office to a Known Working Build
Important: After rolling back, you may want to temporarily disable automatic Office updates to prevent the system from automatically reinstalling the problematic build.
Free Microsoft Office alternative

Tired of Update Errors Disrupting Your Work? Try WPS Office

Frequent updates in Microsoft Office can sometimes break existing workflows and database connections. While WPS Office does not feature a direct database equivalent to Access, it offers a highly stable, lightweight, and completely free alternative for your word processing, spreadsheet, and presentation needs. Enjoy seamless compatibility without the frustration of forced, buggy updates.

  1. 1. Download the Installer: Visit the official WPS website and download the free installation package.
  2. 2. Install WPS Office: Run the installer and follow the simple on-screen instructions.
  3. 3. Start Creating: Open WPS Office and begin editing your documents, spreadsheets, and presentations immediately.
Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx)Stable performance without forced updates disrupting your daily workflowLightweight software that consumes minimal system resourcesFamiliar tabbed interface for a seamless migration experience
microsoft office alternative - wps office

Frequently Asked Questions

Why do my linked SQL Server records suddenly show #Deleted in Access?

This issue is typically caused by a bug or compatibility problem introduced in a recent Office update (such as version 2205). It most commonly occurs when a text field is used as the primary key in the linked ODBC table.

How do I fix update error 30183-27 (400) when rolling back Microsoft Office?

Error 30183-27 (400) usually indicates a network or security block. You can fix it by temporarily disabling your proxy settings, antivirus software, and firewall before retrying the update via File > Account > Update Options.

Will changing my database primary key fix the #Deleted error permanently?

Yes, redesigning your database table to use a numeric data type (like an auto-incrementing integer) instead of a text field for the primary key is a known permanent fix for this specific ODBC linking issue.