Forum Discussion
GontranHarvey
Jan 16, 2023Brass Contributor
ODBC tables connection problem since 16.0.15831.20216
The new update 16.0.15831.20216 has a bug when connecting ODBC tables. When I execute this code: Set tdf = CurrentDb.CreateTableDef(strCurrentTable, dbAttachSavePWD, strRemoteTableName, strC...
- Jan 16, 2023
Hi Gontran,
The problem and potential workarounds are documented in our bug tracking blog.
Servus
Karl
****************
Access Bug Trackers
Access News
Access DevCon
nikos_d
Jan 18, 2023Copper Contributor
Hi all,
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.
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.
Tom_van_Stiphout
Jan 19, 2023Steel Contributor
While you're reverting: also switch away from Current Channel. Way to aggressive in most business situations.
- nikos_dJan 19, 2023Copper ContributorIn our case, this is not feasible, because our MSAccess Application customers are using whatever Office version they have already purchased.
- Tom_van_StiphoutJan 20, 2023Steel ContributorThe 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!- nikos_dJan 22, 2023Copper ContributorThat is a good suggestion. We will promote the idea to revert to the Semi-Annual Enterprise channel to our customers. Thanks