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...
I'm having a similar issues I found this... I can't use the work arrounds he proposed but maybe your can
https://codekabinett.com/rdumps.php?Lang=2&targetDoc=msaccess-bug-v2205-odbc-deleted-nvarchar-primary-key
- 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.
- 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.
- 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.
