I have a client where I had the problem connecting to the SQL Server when they enabled TLS 1.2. I didn't think they had the connection over Internet. I am pretty sure it was via WAN. But I will see what protocol is set there; and see how changing to named pipes protocol will help. Frankly, I don't know what it is. But I am willing to try anything.
As I wrote to you, in another message, your suggestion to use CAST with the SQL Server Native Client and VARCHAR(MAX) works. And the SQL Server Native Client has no problem with TLS 1.2. Maybe this will be my solution.
Thank you!
>>Thank you. The problem with the
driver={Sql Server};is the TLS 1.2. But you already know that :)
>
>That should only be a problem if you're connecting to the SQL server over the Internet which in general is a terrible idea. If you directly connect over a local WAN connection this won't be an issue. Or use named pipes protocol.
>
>+++ Rick ---
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
