SQL Server update breaks Access Linked Table Application (1 Viewer)

Did the Nov 2014 SQL Server Patch affect your Access Linked Tables

  • Yes - I Use the SQL Server Native Client Pre version 10.0

    Votes: 0 0.0%
  • No - I use Native Client Pre 10.0

    Votes: 0 0.0%
  • No - I use the ODBC that came with the Operating System

    Votes: 0 0.0%
  • Yes - I use something different

    Votes: 0 0.0%
  • No - I use something different

    Votes: 0 0.0%

  • Total voters
    2
  • Poll closed .

Rx_

Nothing In Moderation
Joined
Oct 22, 2009
Messages
2,803
Don't Panic
(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

Code:
[COLOR=#555555]Posted: 20 Nov 2014 07:41 PM PST[/COLOR]
[COLOR=#000000]My inbox has been flooded by [URL="http://www.infoworld.com/article/2848574/operating-systems/microsoft-botches-kb-2992611-schannel-patch-tls-alert-code-40-slow-sql-server-block-iis-sites.html"]reports[/URL] 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 [URL="http://darrenmyher.wordpress.com/2014/11/13/security-update-ms14-066-causes-major-performance-in-microsoft-access-sql-server-applications/"]Darren Myher.[/URL]
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 [URL="https://accessexperts.com/blog/2011/03/24/sql-server-connections-strings-for-microsoft-access/"]post.[/URL]
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:
[URL]http://www.microsoft.com/en-us/download/details.aspx?id=36434[/URL]
Downloading Native Client 10 is a little more complex, first navigate to this page:
[URL]http://www.microsoft.com/en-us/download/details.aspx?id=16978[/URL]
Click on the plus sign next to [B]Install Instructions[/B]
Navigate down the long page to the section titled
[B]Microsoft® SQL Server® 2008 R2 Native Client[/B]
[/COLOR]
 

Rx_

Nothing In Moderation
Joined
Oct 22, 2009
Messages
2,803
My server already had Native Cleint 11.0. The indications are that the update only affected those Pre- Native Client 11.0.
Yes, we would all appreciate people weighing in as to how they fare with the SQL Server Update.
Those considering applying the SQL Server updates may want to schedule them as not to impact the users.
 

kevlray

Registered User
Joined
Apr 5, 2010
Messages
729
Our server/dba staff applies the patches to our various SQL databases. As of yet I do not think that any of our DB's are up to 2012 (still at 2008 R2 for most). It is interesting to note, I needed to download an ODBC driver (for an Excel query project) for a client, but found that the Native Client 10.0 was no longer available, so I had to download the Native Client 11.0, which so far is working just fine.
 

Rx_

Nothing In Moderation
Joined
Oct 22, 2009
Messages
2,803
Guess I had better update my tips with that information.
Just as well, the 10.0 download was hidden better than a Income Tax preperation instruction.
 

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

Top Bottom