>>>>>We have narrowed this down to a connection protocol problem. The software is trying to connect using the Named Pipes Network Library but we require TCP/IP. I have not been able to locate where this setting can be made globally in NT. The only place we have seen it is when setting up a DSN.
>>>>
>>>>Interesting problem, I'd be interested in finding out the answer.
>>>
>>>Well, I would like a cleaner solution but for now, we will just create a DSN for the connection and specify TCP/IP which will toggle the switch for other similar connections. For us and setting up new machines, we can modify the "ghost" used to set up the machines to include this. However, I should think there is a way somewhere to specify the default other than Named Pipes, but I haven't found it yet. If I do, I'll let you know.
>>
>>
>>I don't know if you ever found the solution to this, but if you did -- ignore this:
>>
>>To use TCP/IP instead of Named Pipes you have to include the ADDRESS attribute in your call, and the address is the IP address. For example:
>>
>>omain.conhand1 = SQLSTRINGCONNECT( SQLDRIVER=SQL Server; SERVER=EDispatch ; UID=sa; PWD=; WSID=EClient; DATABASE=Dispatch; ADDRESS=123.123.123.123,1433)
>>
>>Note the port in on that address, but I have been successful using just the IP address without the port. It also wouldn't hurt to put the NETWORK attribute on which would be Network=DBMSSOCN for the 32-bit Sql Server TCP/IP DLL.
>
>Thanks for the info Valerie.
>Bill

Bill/Valerie, I know this is a year old, but it's right along the line of what I want to do - namely somehow passing that I want to use TCP/IP (as opposed to Named Pipes, etc.) in my connection string. Does the 'Network=DBMSSOCN' alone do this or must I specify the 'ADDRESS=123.123.123.123,1433' portion? If the latter is the case, can that accept a domain name such as "ADDRESS=MYSERVER.COM"?

also - where can I find complete documentation on the connection string paramters/clauses - I never even new there was an "ADDRESS" parameter available.

Thanks,