>>>
>>>If you are absolutely sure that the 32 bit driver is installed, then change the program to fetch the reason why the connection failed - AERROR() will populate an array with the information on the condition that is leading SQLCONNECT() to return -1.
>>
>>The error is "no connection could be made because the target machine actively refuses it". I guess my test PC does not like the Devart driver. It was a nice try though.
>>Thank you.
>
>Dmitry, it seems like a network connectivity error. Since the other drivers are reaching the target server (aren't they?), could it be the case that the SQL Server is not listening to the default 1433 port?
>
>You may try to change the reference to the server in
>
>#DEFINE SERVER_NAME "YourServerNameOrAddress"
>
>to
>
>#DEFINE SERVER_NAME "YourServerNameOrAddress\InstanceName"
>
>or, after finding out which port is being used, to
>
>#DEFINE SERVER_NAME "YourServerNameOrAddress,PortNumber"
>
Your suggestions was right on the money! I didn't have to specify the Instance name or the port. But I went to the Configuration manager and saw that the TCP/IP protocol was disabled. I enabled it and now the test PRG that you created works. Thank you!
And the Devart ODBC works with the varchar(max). So I know there is an alternative solution.
"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
