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...
KenzoSoZy
Jun 01, 2022Copper Contributor
I use MySQL from Access via MySQL ODBC Driver,
after 2205 update, some of tables also display #delete.
first aid
Restore from 2205----> to 2204
open command prompt (admin mode)
(paste)
cd %ProgramFiles%\Common Files\Microsoft Shared\ClickToRun
(next line paste)
officec2rclient.exe /update user updatetoversion=16.0.15128.20248
then automatically rollback
after this
Access account info panel
office365 autoupdate----> off
until this problem is solved
after 2205 update, some of tables also display #delete.
first aid
Restore from 2205----> to 2204
open command prompt (admin mode)
(paste)
cd %ProgramFiles%\Common Files\Microsoft Shared\ClickToRun
(next line paste)
officec2rclient.exe /update user updatetoversion=16.0.15128.20248
then automatically rollback
after this
Access account info panel
office365 autoupdate----> off
until this problem is solved
- JoneSh77Jun 01, 2022Copper Contributor
Hi
We have the same problem with postgresql tables linked via ODBC driver
For the moment we have two solutions :
The first is to change all the tables having a non numeric primary key by adding a new numeric key (sequence) and keeping a unique constraint for the former one . It seems to work but it represents some work ..
The second solution is to use the Postgresl ODBC ANSI driver instead of the UNICODE driver. It makes the job for us
The best would be to solve the bug inside Microsoft Access but for the moment i have seen no news about it.
regards
- LaraDuttonJun 02, 2022Copper Contributorthis 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."
""- JoneSh77Jun 03, 2022Copper ContributorHi
I have updated Access today and it works fine again. The problem seems to be solved
Thanks