Others

Fix Access 365 Error With AFTER INSERT Triggers on Linked SQL Server Tables

Algirdas Jasaitis Oct 19, 2026 868 views

Question details

Users experience an error in the 64-bit version of Access 365 when trying to insert records into a linked SQL Server table that has an enabled AFTER INSERT trigger.

How to Fix Access 365 Error When Adding an AFTER INSERT Trigger to a Linked SQL Server Table

Product: Microsoft Access 365
Device & OS: not provided
Scenario: Inserting records into a linked SQL Server database table through the Microsoft Access 365 interface.
Observed behavior: The application throws an error indicating that the target table cannot have enabled triggers when the statement uses an OUTPUT clause without an INTO clause. This issue primarily impacts the 64-bit version of the software.

Before you start

Ensure your computer is connected to the internet, as Microsoft engineers frequently push remote background fixes for this specific query issue without requiring a full application update.

Solution 1Recommended

Apply the Microsoft Remote Fix

Microsoft has deployed a remote background fix for this specific OUTPUT clause error. Allowing your Access client to sync with Microsoft servers is usually the safest way to resolve the problem.

Because this issue was addressed via a remote fix by the Access engineering team, you do not necessarily need to wait for a major version release. The fix applies to your current build once the client communicates with the server.

Close the application

Close all active instances of Microsoft Access 365 and any open database files on your computer.

Connect to the internet

Verify that your computer has an active, stable internet connection so the Microsoft Office background services can retrieve the latest configuration updates.

Test the database insert

Reopen Microsoft Access 365, connect to your linked SQL Server table, and attempt the record insert operation again.

Force a manual update

If the error persists, manually prompt an update by navigating to File > Account > Update Options and clicking 'Update Now'.

Remote Fix Applied: If successful, the records will insert smoothly without needing to alter your SQL Server backend.

Solution 2

Temporarily Remove AFTER INSERT Triggers

If the remote fix is not yet available for your specific build or region, disabling the trigger on the SQL Server side allows inserts to proceed.

Solution 3

Revert to the 32-bit Version of Access

Since this bug exclusively affects the 64-bit architecture of Microsoft Access 365, rolling back to the 32-bit version avoids the OUTPUT clause error entirely.

Free Microsoft Office alternative

Looking for a Lightweight, Reliable Office Suite?

While WPS Office does not include a direct database replacement for Microsoft Access, it serves as a highly efficient, free alternative for your core productivity needs. If you are frustrated by heavy updates and software bugs in Microsoft 365, try WPS Office for processing documents, spreadsheets, and presentations seamlessly.

1. Visit the WPS website: Go to the official WPS Office website on your computer.
2. Download the software: Click the download button to get the free installation package tailored for your operating system.
3. Install and enjoy: Follow the simple on-screen instructions to install the suite and begin editing your documents immediately.

Fully compatible with Microsoft Office formats including DOCX, XLSX, and PPTX.Lightweight installation with blazing fast startup speeds.Familiar ribbon user interface requiring zero learning curve.Free core features to replace Word, Excel, and PowerPoint.

microsoft office alternative - wps office

Frequently Asked Questions

Why does this error only affect the 64-bit version of Access 365?

The error stems from a specific bug in how the 64-bit Microsoft Access client processes the OUTPUT clause when communicating with SQL Server. The 32-bit architecture handles the data return differently, which naturally bypassed this specific trigger conflict.

Where can I find real-time status updates for Microsoft Access bugs?

Microsoft does not always publish minor remote fixes immediately in public support articles. However, significant updates and temporary workarounds are often shared in Microsoft Tech Community forums or by Microsoft MVPs shortly after patches are deployed.

Will disabling the AFTER INSERT trigger cause data loss?

Disabling the trigger will not cause data loss for the inserted record itself, but any automated backend processes relying on that trigger (such as audit logging, cascading calculations, or updating related tables) will fail to execute. Always consult your database administrator before disabling SQL Server triggers.

Office Quick Solutions