Forum Discussion
Qassimi90
May 30, 2022Copper Contributor
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...
LaraDutton
May 30, 2022Copper Contributor
I'm having a similar issues I found this... I can't use the work arrounds he proposed but maybe your can
Qassimi90
May 31, 2022Copper Contributor
We try to use ODBC Driver 17 for SQL Server but nothing change. I need to find others solution. Thank for the help.
- George_HepworthMay 31, 2022Silver Contributor
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.
- Qassimi90Jun 01, 2022Copper Contributor
- No, we tested only one of the affected computer.
- ODBC Driver 17 already available in the computer but previously we only use SQL Server Driver.
- We setup a new DSN using ODBC Driver 17, import the tables back and check them. The result is still the same #deleted fields display.
- We using .mdb, not .accdb.
HQ already request us to downgrade the Access to 2016 version. So that is our solution for now.
- George_HepworthJun 01, 2022Silver ContributorI've added your experience to the reports to Microsoft. This is particularly unsettling as it represents a different variation on the problem. We also see that other databases, such as Postgres, are being impacted the same way.
- JlorbzMay 31, 2022Copper Contributor
I can confirm that we are having a very similar issue on some machines. Afflicted machines have MS 365 Office Version 2205 Build 15225.20204 CTR and our single machine which is working normally is on 2204 (Build 15128.20248). Reviewing version notes there doesn't seem to be changes that would cause this but still it has. I changed the data format to VarChar and can view the data normally. Going to stick to that for now.