>Here what prompted me to ask the question (start this thread).
>I have a customer with many PCs using my VFP application with the legacy ODBC driver ("SQL Server"). Works for many years (aside from my bugs :).
>A couple of days ago IT sends me an email that one PC has a problem connecting to the SQL Server. The error message points to the SSL. I have seen this error once before with another customer and it was resolved when they enabled TLS 1.2. Now, keep in mind that we are talking about just one PC; nothing changes on the SQL Server, nothing changed on the VM server where configuration files reside. The IT said that the Honeywell rep was trying to change something on this PC (for his program) and most likely changed something. (Needless to say that I already sent some people to get rid of the Honeywell rep :).
>Back to the story. I asked the IT to enable TLS 1.2. He said he did but the same error. I really don't know if he did or how he did it. So, I was trying to understand how to enable TLS 1.2 on a PC better before I ask the IT to let me connect to the PC. I also offered the IT to replace the ODBC driver with the newer, Native. But he wrote "Since everything works everywhere else, I don't want to change anything, just because of this PC"

It may have to do with the version of the ODBC driver on that PC, that may not support TLS 1.2
*