Forum Discussion
ODBC tables connection problem since 16.0.15831.20216
Hi Gontran,
The problem and potential workarounds are documented in our bug tracking blog.
Servus
Karl
****************
Access Bug Trackers
Access News
Access DevCon
We have the same issue in all of our customer installations running any version above 15831.20208
We are reverting all our customers to version 15831.20208 in order to be able work.
We hope this major issue will be fixed soon in a new version.
Hi,
> We hope this major issue will be fixed soon in a new version.
A fix is planned for next week. I have updated the already mentioned doc article.
Servus
Karl
****************
Access Bug Trackers
Access News
Access DevConHi,
The new version 2301 (Build 16026.20146) released in the Current Channel today, should provide a fix for this bug. Please report if it worked for you.
It can take a few days to roll out new versions. Those affected by the bug can actively request it with Update Now.
I will also report on the effects or side effects in my documentation article.
Servus
Karl
****************
Access Bug Trackers
Access News
Access DevCon- Good to know this is fixed.
As Tom_van_Stiphout suggested, we are moving our clients to the semi-annual channel, so I have not tested if the new version works for us. If we have any further issues, I will let you know.
Thank you for letting us know Karl.
- Thanks Karl
- Me I'm lucky because I'm using the same codeDB for all my connections for all my clients, so I only had to change one line of code Replace("MyRemoteTableName","dbo.","") and that's it. Should be a good Insight for people who like to copy code.
Again Karl, thank for your work on that.
- While you're reverting: also switch away from Current Channel. Way to aggressive in most business situations.
- In our case, this is not feasible, because our MSAccess Application customers are using whatever Office version they have already purchased.
- The channel has nothing to do with the version.
While clients make the final decision, you can advise them, and tell them if they don't want to be on the bleeding edge, they should revert to Semi-Annual Enterprise channel. Let others deal with the bugs!
- Here all you need :
https://www.accessforever.org/post/naming-of-linked-sql-server-tables-is-inconsistent- Thank you for the link. Good to know that it will be fixed soon.
