Hi <your name goes here>
Could you do us a favor and include the entire thread going forward. Some of use respond through email only and would have to backtrack to make sure we know what was being discussed.
Thanks for the link. I've read articles suggesting the use of the OLE DB driver. I'm not sure if this is just going to be another fad like "stop using DAO and code everything in ADO" that was the mantra for Office 2000. Then Office 2003 reversed that saying use the DAO library and only use ADO with SQL server databases that are not linked to your Access database.
Also, I didn't see anything directly referring to MS Access, nor do I recognize any of the contributing authors in either article as being Access developers. I may not know every Access developer but I sure know all the heavy-hitting MVPs.
I, personally, would stick with SQL native client. Access has not grown to use the features that have been added to the latest SQL Server engine.
Regards,
Bill Mosca
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Monday, August 06, 2018 3:09 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] SQL Server Native Client 11.0 - Some advice please
Bill,
As always thanks for your input. A member of another form weighed in with this interesting article. In summary,
This 2017 article from MS recommends not to use the Native client going forwards and to use the OLE DB driver instead. Here is the article:
Although I have not decided to chase this rabbit, at least if I decide to do so, it will be the RIGHT rabbit!
Posted by: "Bill Mosca" <wrmosca@comcast.net>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (4) |
Tidak ada komentar:
Posting Komentar