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.

Thanks Evan CI, I will check with the older connections and see if my channels have also been fixed.

Hey KumarG_108, I'm not entirely sure about your use case, but I'm just confirming here on my end, but I think the latest update to be pushed to the current channel (Version 2202, Build 14931.20132) may have resolved this issue. I've changed nothing on my test machine except for updating to the latest version, and I'm able to see the values in these tables again. I'm going to run a few more tests here and confirm, but I believe this problem may be resolved now. Thanks!

We also started having the same problem with some 43 tables. We use Office 365. I was able to resolve the problem to some degree by adding a second Microsoft to Oracle ODBC that connects after the Oracle ODBC. Its seems to work. All our systems are broken and I had to work many evenings and weekends on this. I think it may have been a MS patch that came thru. It was like a virus spreading from one user to the next. I am still trying to fix each system as table names need to be corrected in the code as well as the linking.

Hi, We seem to be running into this issue as well. We have some vendor supplied Oracle tables that we were connecting to in Access with an Oracle 19c driver, and any version of office after the locking issues were resolved (Version 2201 Build 14827.20158 I believe). I did find an issue in 2020 where Access was not properly identifying AutoNumbers, but I'm not sure if that's the same case here. Here is the link to that forum post. What we had ended up doing to avoid the lock file issues, and now this linked table issue, is block our updates and stay on Version 2112 Build 14729.20260, this seems to resolve all issues. Even the latest update from Feb 8 2022 still shows #deleted records in any linked table from our Oracle data sources. The only thing that has been changing on our setups is the version of Access, which also leads me to believe there is an issue with Access and linked tables. Thanks!

I don't have any other thoughts, then, unless it has to do with the ODBC driver for Oracle.

MS Access Displays #Deleted in Every Field for Certain Tables

Anonymous

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.

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

Anonymous

2022-03-09T13:53:00+00:00

Thanks Evan CI,

I will check with the older connections and see if my channels have also been fixed.
Was this answer helpful?

0 comments No comments
Anonymous

2022-03-09T13:44:26+00:00

Hey KumarG_108,

I'm not entirely sure about your use case, but I'm just confirming here on my end, but I think the latest update to be pushed to the current channel (Version 2202, Build 14931.20132) may have resolved this issue. I've changed nothing on my test machine except for updating to the latest version, and I'm able to see the values in these tables again. I'm going to run a few more tests here and confirm, but I believe this problem may be resolved now.

Thanks!
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2022-03-08T20:04:24+00:00

We also started having the same problem with some 43 tables. We use Office 365. I was able to resolve the problem to some degree by adding a second Microsoft to Oracle ODBC that connects after the Oracle ODBC. Its seems to work. All our systems are broken and I had to work many evenings and weekends on this. I think it may have been a MS patch that came thru. It was like a virus spreading from one user to the next. I am still trying to fix each system as table names need to be corrected in the code as well as the linking.
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2022-02-14T13:29:53+00:00

Hi,

We seem to be running into this issue as well. We have some vendor supplied Oracle tables that we were connecting to in Access with an Oracle 19c driver, and any version of office after the locking issues were resolved (Version 2201 Build 14827.20158 I believe). I did find an issue in 2020 where Access was not properly identifying AutoNumbers, but I'm not sure if that's the same case here. Here is the link to that forum post.

What we had ended up doing to avoid the lock file issues, and now this linked table issue, is block our updates and stay on Version 2112 Build 14729.20260, this seems to resolve all issues. Even the latest update from Feb 8 2022 still shows #deleted records in any linked table from our Oracle data sources. The only thing that has been changing on our setups is the version of Access, which also leads me to believe there is an issue with Access and linked tables.

Thanks!
Was this answer helpful?

6 people found this answer helpful.

0 comments No comments
George Hepworth 23,120 Reputation points Volunteer Moderator

2022-02-02T00:51:45+00:00

I don't have any other thoughts, then, unless it has to do with the ODBC driver for Oracle.
Was this answer helpful?

0 comments No comments