Forum Discussion
gil_gentien
May 30, 2022Copper Contributor
Office pro 2021 version 2205 build 15225.20204 Bug access sql linked table #delete
I have bug with this new version , some off my linked table (slq native client 10) diplay #delete in all colums. I have other computers with an old version they work perfectly. What can i do to s...
LaraDutton
Jun 02, 2022Copper Contributor
this is from another thread I'm on, I can't validate as the move to ODBC 17 work as a fix for me yesterday...
""
George Hepworth replied to George Hepworth
Jun 01 2022 04:11 PM
The MS Access team is reporting that this is now fixed.
"This should be fixed now in Current Channel (Preview) channel now, and the fix should be in Current Channel tomorrow."
""
""
George Hepworth replied to George Hepworth
Jun 01 2022 04:11 PM
The MS Access team is reporting that this is now fixed.
"This should be fixed now in Current Channel (Preview) channel now, and the fix should be in Current Channel tomorrow."
""
JoneSh77
Jun 03, 2022Copper Contributor
Hi
I have updated Access today and it works fine again. The problem seems to be solved
Thanks
I have updated Access today and it works fine again. The problem seems to be solved
Thanks
- JoneSh77Jun 07, 2022Copper Contributor
Hi,
Sorry for the delay
I have Microsoft Access Version 2205 Build 16.0.15225.20172 64bits version
Since friday it works again for me with sql server and with postgresql
Best regards- annz-vtJun 07, 2022Copper Contributor
Thanks, I can confirm this also - 32-bit version 2205 build 15225.20204 no longer causes tables with an nvarchar in the Primary Key display as #Deleted
- annz-vtJun 03, 2022Copper Contributor
Hi - thanks for the update. Could you (or anyone else who has received the fix) post your current Office version and channel? It still hasn't shown up for me.
Thanks.
- isladogsJun 03, 2022MVPFor 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- cbgbnyc1Jun 06, 2022Copper Contributorno I don't think it is out