Microsoft changed course about this.
The current (as of March 2020) state of affairs about ODBC is quite clear, actually:
<quote> ODBC is the primary native data access API for applications written in C and C++ for SQL Server. There is an ODBC driver for most data sources. Other languages that can use ODBC include COBOL, Perl, PHP, and Python. ODBC is widely used in data integration scenarios. </quote>
On Wed, Apr 8, 2020 at 6:45 PM Frank Cazabon frank.cazabon@gmail.com wrote:
Thanks Richard, I vaguely recall seeing that ODBC was no longer being developed/used, hence my doubt about using it.
Frank.
Frank Cazabon
On 08/04/2020 01:20 pm, Richard Kaye wrote:
I got away from the NC drivers a long time ago. Currently using 17 for
pretty much everything.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of António
Tavares Lopes
Sent: Wednesday, April 8, 2020 11:12 AM To: profoxtech@leafe.com Subject: Re: SQL Server 17 - ODBC or Native Client?
Frank,
With SPT, there is no big feature difference between NC and recent ODBC
drivers. If you're using NC, you can safely migrate to the more recent drivers.
You may find bigger differences between the old "SQL Server" driver and
the following versions because of the way they handle SQL datatypes, and how they are mapped into VFP. But if you're already using NC then you won't face new issues.
On Wed, Apr 8, 2020 at 3:40 PM Frank Cazabon frank.cazabon@gmail.com wrote:
Hi,
I'm testing a VFP app against a SQL Server 2017 database. I use "DRIVER=SQL Server Native Client 11.0" in my connection string for SQL Server 2012 and 2014. I don't think there is a newer version of Native Client than 11. Should I be using the "Driver={ODBC Driver 17 for SQL Server}" instead?
--
Frank.
Frank Cazabon
[excessive quoting removed by server]