A family of Microsoft relational database management systems designed for ease of use.
Issue seems to be fixed in March 08 Version 2201 14827.20220 Monthly Enterprise as well, though no mention of the issue or fix is in the update notes.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We use an ODBC connection to bring some tables from a vendor supplied database into MS Access so that users can create their own on demand queries without needing to know SQL. Some of those tables, not all of them, have started to have problems in MS Access so that every field is populated with #Deleted when we try to open the table. We can query these tables fine using pl/sql Developer.
This seems to indicate that the problem is with the version of MS Access. I've been looking for other reports of #Deleted and what I can find are from 6 or 7 years ago and not very many are recent reports. Does anyone have an idea for a workaround? We hate to lose the ability for our users to utilize MS Access for querying these tables.
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Issue seems to be fixed in March 08 Version 2201 14827.20220 Monthly Enterprise as well, though no mention of the issue or fix is in the update notes.
Our pass thru proc seems to run ok. It looks like they finally fixed it. Near the end of December 2021 there was another issue that stopped users from being able connect due to locking issues which lasted about 3 weeks. Are they properly testing a fix or change or patch?
As the original poster, our MS Access version has recently updated and we are finally able to see our table data. We are now on version 2201 (Build 14827.20192).
Thanks for the support from other users encountering this same issue and I hope an upgrade will soon come your way that resolves your problem. And even more so I hope that this problem doesn't creep back into a future release of Access.
Hi I noticed that the update was done for the 32 bit version that now works for my systems but the 64 bit version still has the issue. It has not updated to the current version yet. Is anyone else still waiting for the 64 bit version? Thanks
A different angle on this problem.
I was connecting to an Intersystems database over ODBC using Linked Tables and when our database people upgraded the database version, and pushed us onto a new version of the ODBC driver, I ended up getting #Deleted appearing for every cell of every field of my linked tables.
It turned out to be caused by the new database switching to using BigInt (Large Number) data type and my database was not able to deal with this.
Luckily my MS Access was new enough that I did not need to update the program (apparently anything newer than Access 2016 build 16.0.7812 should be fine). But I did need to go into the Current Database options and enable the "Support Large Number (BigInt) Data Type" option (while I was there, I also enabled the Support Date Time Extended (DateTime2) Data Type"). This irreversibly updates the ACCDB file to Access 2016, so it cannot then be opened in older versions of Access anymore. (https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=BNETODBC\_INTRO)
Lastly, i had to go into Linked Table Manager ... select my linked tables and click Refresh in order for Access to apply the BigInt data type into my actual tables. (https://support.microsoft.com/en-au/office/using-the-large-number-data-type-5b623f6e-641d-4e97-8bdf-b77bae076f70)
After doing this, i was able to view my Linked table fine again... and also run queries against it without any problems.