>Use the SQL Server Client Configuration Utility to define the database and the ip address. You will probably have to use a static address and use something like 161.24.63.20, 1433. 1433 is the default port used by SQL Server. I had set this up once before on a WIndows 95 machine. I used the SQL Server CD to install the Client Utilities and then added the server name and port. Installing on a WIN95/98 machine only allows the client utilities. I did this for a SQL Server project on the network of my Internet ISP. Once I was logged into the net, I had access to the NT SQL Server machine. I was also able to us BCP etc. from the client machine to copy data from the remote server.
>
>In essence, you don't have to do very much. If you can dial in to the remote network using RAS, TCP/IP will give you access to the SQL Server if you have its name or ip address (and authorization).

Thanks for the additional info. I did get it to work, sort of. For the first try I got NetBEUI to work. With the additional TCP/IP info you gave me I will try that as well.

I am now able to create the ODBC entry and the test connection works, but when I run the application I get a ODBC error: Function Sequence Error. I tried looking in MSDN and found out that the error is S1010, but that's about all.

The program works on my development machine, but not the client - even when I connect their machine to our LAN.

TIA for any help.