Many people are reporting that the OpenDatabase method no longer works and also reports an Error 3050: Cannot lock file. Other Side Effects Of This Bugīe forewarned that other issues have now surfaced caused by this same bug. So you may wish to keeps your eyes open for these 2 extra updates as well until Microsoft properly fixes the issue.
The full fix for 2013/2016 MSI will be released in the Windows Update catalog in the February update (probably February 1st), but there will be an update available in the download center before then (customers can contact customer support to get the link for this update when it is available). The updates KB5002115 and KB5002124 do not include the full fix, they do contain the partial fix that address UNC paths.
I have had several sources now formally state, after confirming, that KB5002115 and KB5002124 both also contribute to this issue as well. If that still doesn’t work then your only solution remains to disable automatic updates and then rollback your installation to a previously stable build number. So, should you be one of those lucky people that continue to experience the issue after updating to the most recent build number, then try directly linking your tables using IP based paths (eliminating all networking layers). So clearly some major networking issues remain to be fixed! This is why I do not understand how Microsoft has already labelled the issue as ‘Fixed’ on their official page on the matter. Hard links, Junctions and Symbolic links Access Dev Team Our team is currently working on a fix for the following network paths: Important: Currently, the applied fix only addresses standard UNC paths. Some people get the good stuff, some get okay help and the rest of you are simply out of luck! □ Tell me it isn’t so Microsoft! Makes me think of 2 & 3 tier health care system, different class of citizens. It is interesting how the fixes for different versions are being released on different timelines.
Microsoft has finally started releasing another update to fix what the first fix did not fix! As it stands right now, they seem to have release a ‘proper’ fix for:
Access for Microsoft 365 Access 2021 Access 2019 Access 2016 Access 2013 More.Less What’s Been Fixedįrom the above webpage, the following is how things stand as of :