All fields have a value of #deleted in linked SQL server tables (1 Viewer)

[RogerCooper]

I am suddenly getting values of #deleted in all fields in tables connected to 2 different SQL server databases, which have functioning for years. This affects most of the tables in the databases, regardless of the number of fields or records (I have 13 record, 2 field table that is affected) but a few tables with only a small number of fields are unaffected. Rebooting, reconnecting does not help. Any idea of what the problem could be.

 

[Gasman]

Does no-one do a search anymore?

Just one of many.

New Access / SQL backend bug - #Deleted showing in Tables

Views will be equivalent to snapshots with the data not being editable. That's why they will not be effected. Good luck fixing the rest. Thank you for reminding me about Views, as I'm a little green.

www.access-programmers.co.uk

 

[RogerCooper]

I did a web search on this, but no one had the same issue. People had some records or some fields with #deleted but no one had all fields & records affected.

 

[Gasman]

Not sure how you can delete a field?
Check the link and what version you have.
This has been going on for the best part of a week.

 

[RogerCooper]

If you delete a field in an SQL Server table, that can cause #Deleted issue when viewing the table in Access.

 

[The_Doc_Man]

Yes, but the "values of #deleted in all fields in tables" (my emphasis added) is the bug introduced by that particular patch called out by Gasman.

 

[GPGeorge]

Just in case you haven't yet gotten the word on this, MS Access team notified us that the fix is being deployed now. Look for update to version 2206. It's going to arrive at different times depending on what update channel you are on. It's not available to yet today, but others are reporting that is has been for them.

Also, it would be nice to get feedback from a number of users on whether 2206 actually fixes the problem for all of them. Not that the recent rapid pace of bug releases has shaken anyone's confidence about such things....

 

[RogerCooper]

Thank you for making that clear, I was not aware of this being an Access bug.

 

[RogerCooper]

2206 is a beta build. How far should I roll back to fix this issue?

 

[theDBguy]

2206 is a beta build. How far should I roll back to fix this issue?

I could be wrong, but I think you can go back to 2204. If not, then maybe 2203. Good luck!

 

[GPGeorge]

2204 works.

What makes you say 2205 is a "beta build"? What does that even mean?

 

[isladogs]

I'm still waiting for the 2206 update to become available here ....

 

[isladogs]

For info, MS have just announced that the #Deleted bug fix is now available to all in the Current Channel, Current Channel (Preview), Beta, and Semi-Annual Channel (Preview).
It does not require a new build but will require closing and restarting Access to see the change. In other words, the fix was done by rolling back the change that caused the problem

Just tested & now working for me