Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SQL Server Driver vs more recent ODBC driver
Message
 
 
To
22/11/2018 01:26:45
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Database:
MS SQL Server
Miscellaneous
Thread ID:
01663573
Message ID:
01663681
Views:
45
>Dmitry,
>
>No contradiction here. TLS support has nothing to do with how the data is being handled and interpreted, but how the connection is made (particularly, how it is being secured).
>
>Devart supports SSL, don't know about TLS. It would be nice that Naomi could be able to test, I don't have an environment for it.

I don't have TSL1.2 here, it's a client of ours who is moving to this and he first notified us about the problem with SQL Server driver we were using. Using your program to test I found that from the drivers I already had installed locally only SQL Server driver supported varchar(max). All other cases returned C(0).

So, we're in a predicament for our VFP applications that use DSN (ODBC connection) for connecting to SQL Server. We do use varchar(max) and varbinary(max) types. I'm not sure I understood what Pavel Celba was suggesting.

Is there a simple way for us to have our applications working assuming that this driver will be unavailable? Is there any other driver that can work with SQL Server, doesn't experience the varchar(max) problem and is free?

Thanks.
If it's not broken, fix it until it is.


My Blog
Previous
Reply
Map
View

Click here to load this message in the networking platform