I think my problems may have been that I also have an ISDN Adapter attached to one of my PCs connected to SQL Server. When I changed my SQL settings to use TCP/IP, things started going stupid. I did change both ends of the connection.

>Are you using TCP/IP as a SQl server protocol? By default it is set up I believe with only Named Pipes. Then I think you can configure the individual clients to use TCP/IP in the ODBC setup.
>
>>I've tried removing Named Pipes and all hell breaks loose! Connection becomes lost. It may have been my setup but I'm NOT doing that again!