(Large Friendly Letters)
A re-post of a news item.
As a promoter of the SQL Server Native Client, I wanted to post this and ask anyone if they have encountered this issue?
It appears that the older SQL Server Native Client will break after this SQL Server update is installed. There was no indication of the standard ODBC having this issue.
For myself, I use the latest SQL Server Native Client 11.0. We have not had the problem appear.
If anyone else is doing this, it wouldn't hurt to weigh in.
I have added a Poll for those who use SQL Server Linked Tables
Posted: 20 Nov 2014 07:41 PM PST
My inbox has been flooded by reports around the world of Access suddenly being slow or unusable after the latest set of patches issued by Microsoft.
Turns out one of the patches for SQL Server will in effect render Access applications using the native SQL Server drivers in Windows useless as reported here by Darren Myher.
None of our client applications were affected since we have long migrated all of our clients to SQL Native Client 10 and more recently SQL Native Client 11.
For an example on how to use the native client please refer to this post.
The only drawback to using the client is that it requires installation of either the 32 bit or 64 bit of the driver on every PC using the application. (Select 32 or 64 based on the version of your Windows OS and NOT the version of your Office Suite).
Here are the download links to Client 11:
Downloading Native Client 10 is a little more complex, first navigate to this page:
Click on the plus sign next to Install Instructions
Navigate down the long page to the section titled
Microsoft® SQL Server® 2008 R2 Native Client