[AccessD] ODBC Driver 18 and OLEDB Driver 19 are out

[Arthur Fuller]

Back in the days when I was a code-cowboy, I shared those sentiments. Now I
went to middle-age and opted in a V 1.1. Now in my senior years, I wait for
2.0.

On Wed, Feb 16, 2022 at 3:19 PM Ryan W <wrwehler at gmail.com> wrote:

> ODBC Driver 17/18 are backwards compatible all the way back.   The issue is
> relying on an older driver and missing out on newer features as you
> stated.  So in my case "I like to use the newest version possible".
>
>
>
> On Wed, Feb 16, 2022 at 2:12 PM Paul Wolstenholme <
> Paul.W at industrialcontrol.co.nz> wrote:
>
> > To assist other readers:
> >
> > If you are using anything more recent than SQL Server 2012, you should
> NOT
> > be using SQL Server native client anyway.
> > You can check driver compatibility here:
> >
> >
> https://www.connectionstrings.com/sql-server-native-client-11-0-oledb-provider/
> > If you ever connect to a newer version of SQL Server (or another back end
> > server), that is the time to review which driver is needed.
> > If you do not, you end up with problems using recent features, such as
> > fields using a new data type.
> >
> > I don't "like to use" any driver.  I need to use a compatible one.
> >
> > Paul W
> >
> > On Thursday 17/02/2022 at 5:35 am, Ryan W wrote:
> >
> > Came out yesterday for those that like to use the non native windows
> > drivers for their apps.
> > --
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur