Stream object ADO 2.5 also introduces the and Stream object to represent a stream of binary or text data.

However, i'm not sure, that what i'm doing is futureproof. Record object ADO 2.5 introduces the Record object to represent and manage a row from a Recordset or a data provider, or an object encapsulating a semi-structured data, such as a file or directory. To: c.ConnectionString = 'Provider=MSOLEDBSQL DataTypeCompatibility=80 Data Source=' & svr & ' Initial Catalog=' & db & ' User Id=' & u & ' Password=' & p & ' '

I've tested MSOLEDBSQL after installing the drivers, and changing the (ADODB.Connection) connection string from: c.ConnectionString = 'Provider=SQLOLEDB Data Source=' & svr & ' Initial Catalog=' & db & ' User Id=' & u & ' Password=' & p & ' ' MSOLEDBSQL supports TLS 1.2 and that will be kept updated, according to their documentation: It does not explicitly use TLS, but TLS is always used for credentials according to Microsoft documentation.Īfter looking around i have found that Microsoft released the new provider MSOLEDBSQL as a replacement for SQLOLEDB. it produces an error code 0x80004005 when TLS 1.0 is disabled for SQL Server, because the code still uses the provider SQLOLEDB: I have legacy VB6 code that accesses SQL Server.