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.

I have same for MySQL linked tables with access on latest office version. I'm currently rolling back to the previous version which is allowing users to use the database again. Would be interested to know when this has been resolved.

One poster has suggested that there is an alternative driver for MySQL. Not being familiar with MySQL, all I can say is that you could either rollback to version 2204 or alter the datatype of the Primary Keys or try a newer MySQL ODBC driver if that is an option.

I already have the latest MySQL ODBC Connector driver installed. Still doesn't work. This is a Microsoft problem. They have a bug in their new Office build 2205 update. Please fix it.

Check your PK definitions on those tables. If they are using nvarchar, change them to varchar. That change got rid of the issue for me. @Lisa Greenwood, OMG thank you so much :-D Have a DB I wrote nearly 20 years ago (started with Access 2.0 :-O ) that is still business critical and one simple lookup table suddenly went #Deleted :-( quick change to varchar and it's back up and running :-D

I know the feeling :-) We have similar legacy apps. Glad the change helped you!

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-05-31T13:01:59+00:00

I have same for MySQL linked tables with access on latest office version. I'm currently rolling back to the previous version which is allowing users to use the database again. Would be interested to know when this has been resolved.
Was this answer helpful?

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

2022-05-31T13:09:12+00:00

One poster has suggested that there is an alternative driver for MySQL. Not being familiar with MySQL, all I can say is that you could either rollback to version 2204 or alter the datatype of the Primary Keys or try a newer MySQL ODBC driver if that is an option.
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-01T06:57:23+00:00

I already have the latest MySQL ODBC Connector driver installed. Still doesn't work. This is a Microsoft problem. They have a bug in their new Office build 2205 update. Please fix it.
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-01T10:33:45+00:00

Check your PK definitions on those tables. If they are using nvarchar, change them to varchar. That change got rid of the issue for me.

@Lisa Greenwood, OMG thank you so much :-D Have a DB I wrote nearly 20 years ago (started with Access 2.0 :-O ) that is still business critical and one simple lookup table suddenly went #Deleted :-( quick change to varchar and it's back up and running :-D
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2022-06-01T12:54:32+00:00

I know the feeling :-) We have similar legacy apps. Glad the change helped you!
Was this answer helpful?

0 comments No comments