We have a PB 2019 R2 application connecting to a SQL Server 2016 database using the old SQL Server driver (sqlsrv32.dll).  The OS is Windows 10 Enterprise.  The connection is scripted as follows:

SQLCA.DBMS = lsODBCTrace + "ODBC"
SQLCA.LogId = ls_ap_user
SQLCA.LogPass = ls_Password
SQLCA.AutoCommit = true
SQLCA.Lock = lsODBCLock

lsdbParm = "CONNECTSTRING='Driver={SQL Server};Server=" + ls_sqlca_servername + ";Database=" + ls_sqlca_database + ";UID=" + ls_ap_user + ";PWD=" + ls_Password + "',DisableBind=1,DelimitIdentifier='No',CallEscape='No'" + ",CursorScroll='Static',TrimSpaces='YES'"

SQLCA.DBParm = lsdbParm
Connect;

This code works great but when TLS 1.0 is disabled in the registry this connection fails (see attached error).  We thought we might try using the ODBC 13 driver and so changed the above to this:

SQLCA.DBMS = lsODBCTrace + "ODBC"
SQLCA.LogId = ls_ap_user
SQLCA.LogPass = ls_Password
SQLCA.AutoCommit = true
SQLCA.Lock = lsODBCLock

lsdbParm = "CONNECTSTRING='Driver={ODBC Driver 13 for SQL Server};Server=" + ls_sqlca_servername + ";Database=" + ls_sqlca_database + ";UID=" + ls_ap_user + ";PWD=" + ls_Password + "',DisableBind=1,DelimitIdentifier='No',CallEscape='No'" + ",CursorScroll='Static',TrimSpaces='YES'"

SQLCA.DBParm = lsdbParm
Connect;

Unfortunately that doesn't work.  We are not using DSN profiles or a trusted connection.  Given that, has anyone used the ODBC 13 driver in a PB app with SQL Server and if so, what was your connection string assigned to the DBParm value?  Or is our only option to wait for the R3 release?

Thanks, Tom