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 certain user profile. If I login into the windows using another profile and open the table, the data will be normally displayed.
2. This table are linked table with SQL server 2016, so I have check and find that the table have NVARCHAR field. I try to change the field type to VARCHAR, refresh the table link, then the data can be viewed again.
Current Solution:
1. Delete the user profile and login again. Solve the problems but not sure if it will happen again in the future.
2. Installing Access Runtime. Solve the problems but at the same time i can't debug the program if there something wrong with it.
Does anyone have any idea what happen because i am really lost right now.
I'm having a similar issues I found this... I can't use the work arrounds he proposed but maybe your can
- I should have noted the work around I am using is replacing the nvarchar PK with identity PK and re-adding the old nvarchar PK as a constraint. I have not tried but using a nchar as I read they are similarly effected and would cause more re-coding issues in my environment the the PK replacement. I'm also hoping Microsoft will bet even if the they do it might not be fast enough for my team.
- We try to use ODBC Driver 17 for SQL Server but nothing change. I need to find others solution. Thank for the help.
So to be clear.
- You installed ODBC Driver 17 on ALL users' computers.
- You relinked the tables in your Access FE to use that ODBC 17 driver.
- You distributed that updated Access FE to all users (who now have an Access accdb with links using ODBC driver 17 and they also have the ODBC 17 Driver installed)
- The problem of #deleted fields remains for all of your users with this updated configuration?
If so, we need to know more about YOUR specific situation please.
- 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?
