Forum Discussion
Access 2019 #Deleted Table status (Field NVARCHAR)
Hi, There has been an issue regarding Access 2019 displaying #Deleted status on certain table, for only certain windows user profile. Based on my analysis: 1. This happen to only certa...
This issue seems to be a bug in the most-recent Office 365 update. I support an app that utilizes over 70 linked tables, all to a SQL Server back end. I discovered that, after the 365 update on 5/29/2022, none of the tables linked to any SQL Server table containing an nvarchar field that was part of any unique index, displayed data. I see only "#Deleted" in every cell. My issue had nothing to do with dates (datetime, smalldatetime, etc.). The nvarchar field did not have to be part of the PK. If an nvarchar field was part of any unique index, the ODBC link broke. The only solution for me was to roll back the 5/29/2022 update. After the rollback, everything went back to normal.
- Update to version 2206, which should be available already, or will be soon, depending on your update channel. Also, thanks for the additional detail on unique indexes as well as PKs being problems.
- Good morning, George -
My client is heavily dependent upon Access for a billing application with around 20 concurrent users at any one time processing over 250 million in annual revenue for 1,100 supermarkets. When Access goes down like this, it is a major disruption to the process flow as well as causing the hearts of a half-dozen people (mine included) to stop beating. I am considering advising them to disconnect the auto-update for 365 and take a more cautious approach. Your thoughts?Many, perhaps most, of the MS Access MVPs I know already have stopped
acceptedaccepting auto-updates, or gone to a semi-annual channel so that they stand a chance of such bugs being fixed before they get to them. It's a trade-off between being on the "cutting edge" or the "bleeding edge", you might say. And that's a very fine line, indeed 🙂
