Access linked table to SQL Server database returns "#Deleted"


Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. For more information about this change, read this blog post.


A Microsoft Access-linked table that contains one or more datetime or datetime2 columns and that’s connected to a Microsoft SQL Server database and has a compatibility level of 130 or larger (the compatibility level for SQL Server 2016) returns #Deleted in the results.

When you try to commit record changes to the linked table, you may also receive the following "Write Conflict" message:

This record has been changed by another user since you started editing it.


The issue occurs because the datetime or datetime2 columns contain fractional seconds values. How fractional seconds are handled for datetime2 types was changed starting in Microsoft SQL Server 2016. For more information about the change, see the following articles:


The datetime data type is also affected by the change to datetime2, because the SQL Server ODBC driver converts datetime to datetime2 when it sends data to the server.


Access is introducing a new and improved Date & Time Extended data type beginning in Microsoft 365 Apps Version 2010.

To improve syntax compatibility with SQL, and to increase the accuracy and level of detail in records that include dates and times, Microsoft is implementing the DateTime2 data type in Access. This data type will include a larger date range (0001-01-01 through 9999-12-31) that has better time precision (nanoseconds, instead of seconds). To enable the DateTime2 data type, select New field > Date & Time Extended. For more information, see Using the Date/Time Extended data type.


The Date & Time Extended data type isn't compatible with previous versions of Microsoft Access. As a result, if the data type is implemented within a local Access table and the Access database is used with a previous version that doesn't include this feature, you can't open the database.

You can enable or disable the Date & Time Extended data type for linking and importing operations by using the Current Database Access option Support Date Time Extended (DateTime2) Data Type for Linked/lmported Tables. For more information, see Set user options for the current database.


Access currently doesn't support the use of Date & Time Extended as part of the unique identifier/primary key of the linked ODBC table. If one or more of the columns that make up the unique identifier of the linked table use the Date & Time Extended data type, and the date includes fractional seconds, the record may appear as #Deleted.

For earlier versions of Access, use one of the following methods to work around this issue:

  • Change the compatibility level of the SQL Server database to 120 (the compatibility level for SQL Server 2014) or less.
  • Make sure that the datetime and DateTime2 columns aren't part of the primary key.
  • Add a new column to the table using either timestamp or rowversion data type.
  • Remove fractional seconds from the datetime column(s) using an UPDATE statement.
  • Change the data type from datetime to smalldatetime. Note: This will round values to the nearest minute.
  • If editing data isn't necessary, you may create a query and change the RecordsetType property to Snapshot which will return a read-only recordset that’s not affected by this issue.


Use the Linked Table Manager in Access to refesh the linked table(s) when any design changes are made on the SQL Server.