MS Access Displays #Deleted in Every Field for Certain Tables

Anonymous
2022-01-31T20:26:19+00:00

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.

  • 3 tables that are working have num datatypes for primary key(s).
  • 3 tables that are not working use a combination of num and char datatypes as the primary keys. No bigint datatypes in these tables.
  • There are no pending deletes on the 3 tables that are not working.
  • Since the tables are vendor delivered, we can't change the data structure.
  • A combination of Oracle driver 12.01.00.02 or 12.02.00.01 and MS Access version 2112 build (14729.20194) - the 3 problem tables all show #Deleted in all fields.
  • A combination of Oracle driver 12.02.00.01 and MS Access version 2111 build (14701.20240) - the 3 problem tables work properly and show the data in all fields.

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.

Microsoft 365 and Office | Access | For business | Windows

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.

0 comments

54 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-05-31T01:03:28+00:00

    Me too am having same problem. Version 2205 update is the culprit. Any table with varchar as primary keys are affected with the #Deleted problem. Rolling my Office 365 back to version 2204 has fixed this for now. I'm using ODBC MySQL connector for my linked tables. Microsoft please fix this asap as this is a critical problem. I've many clients affected and not being able to access their database!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-05-26T15:48:13+00:00

    Someone else has posted that the later SQL ODBC Driver Version 17 doesn't suffer from this.
    See this thread for more details : https://www.access-programmers.co.uk/forums/threads/new-access-sql-backend-bug-deleted-showing-in-tables.323388/

    That would also explain why we have only seen it on older legacy systems.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-05-19T02:43:26+00:00

    Today 19/05/22 several of my pcs Access updated to Microsoft® Access® for Microsoft 365 MSO (Version 2202 Build 16.0.14931.20392) 64-bit 

    I now have the same problem as described here.

    I am not able to verify if the 32Bit version has the same problem.

    The Linked Tables in Question were tested on both Microsoft SQL Servers 2014 and 2019

    The Data source is not at issue. nor is the ODBC version, several tried.

    Nor is the type of Access db, db formats from 2000 - 2007 all produce the same result.

    Enabling the "Data Type Support Options" did not change the problem.

    The problem is definitely in Access and is related to Text Primary key.

    The table is Very Simple, A list of User Names with a few other columns.
    The Primary Key was the User Name.

    As a test I created a new Int. column and switched the primary key to it.

    Relinked the table and it is now readable.

    I seem to be lucky enough to have missed the problem in the earlier update.

    THE BEAST IS BACK!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-03-09T19:14:34+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Duane Hookom 26,935 Reputation points Volunteer Moderator
    2022-03-09T14:49:51+00:00

    Have you attempted to create a pass-through query to your tables?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments