This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 32%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFV%3C/text%3E%3C/svg%3E)
In build 2204 all Access linked tables worked fine, but now my users get updates and 20% of my Access linked tables are not working displaying every row/field with: "#Delete". Rolling back every workstation seems like a short term gain as we don't seem to have control over stopping the updates.
What patch or settings change must I deploy to fix this?
What exactly changed in Access so that if needed I can rebuild SQL server tables to allow the link to work?
(In the mean time I have been working to isolate what could be triggering this failure. It does not seem to be as simple as a data type or a size issues like MAX....)
What other possible fixes or workarounds are available?
The seems to affect both 2016 and 365 instances of the 2205 build, in our environment.
As a side note when the linked table is open from the object browser, it shows all data as "#Deleted" as I described above, however if I loop through a DAO Records set based on that link it pulls data fine..... Why?
Let me know if this belongs in another place and what that place is.
Thanks for any help...
Hi @Fritz Vedder
As this issue is related to Access, I would change the tag to be "office-access-dev".
Thanks for your understandings.
Thanks Emilyhua, Is the did you change the tag or is it that you are suggesting that I change it as it currently appears to be "office-access-dev"?
My issue has been resolved, the problem it turns out is only on tables that have a nvarchar datatype as the primary key... Not sure why build 2205 is not playing well with the driver we were using, but ODBC driver 17 should fix this..