"#Deleted" in data fields from external source

[lmnop7854]

Hi there - it has been a long time since I have posted here. I work on a database that is Access based, but our DBAs don't support Access (yeah, that's what I said). So no one knows the answer to my question.

The database our company uses allows us to query using ODBC tables in Access 2010. So far, the data is mapped sufficiently for us to be able to read the data when we query. We do have an external application that we use to create some of the date that we need to append to our database, but the information coming from that source is causing a problem when I query. It is only affecting one table (thank God), but it is a table that most of the organization needs information from. The data now comes to me as "#Deleted" for all of the values that are input from this external source. I know there is something probably very simple that is incompatible with Access 2010, and that is why this is happening.

DOES ANYONE KNOW WHAT THIS COULD BE?

I do have a workaround so that I can change my Query Properties from Dynaset to Snapshot, and that will bring in the data, but that is not a solution for me. This is not just my issue, it could be an issue for lots of other people, so I don't just want a workaround. I would like to know what can be changed, if anything, from the external source of the data.

Please let me know - thank you!!!

 

[Pat Hartman]

When you link to tables, Access caches a lot of information. When table definitions are changed on the server, you need to manually refresh the link to force Access to ask the server for new information.

 

[gfbower]

There are several things that can cause this, but I've found that it is usually bad data in a field such as a null in a number field. This is often generated in a Form field. This error usually requires deleting the specific record from the table where the "#deleted" resides. BUT, always make a copy of the bad record first.
Using Make Query, create a backup copy of the Record - Less the bad field. Delete the bad record from the original table. Then using an Append Query, copy the corrected record back into the original table.