>>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.


If I can recall what I did, I believe I used the client configuration utility and added the server on the advanced tab. You can use an IP address here. I think you add ,1433 in the connection string. By configuring this remote Server, you can then use ODBC to set up the datasource. You will know if it is working when you are able to log in and select the default database.

You may also require a hosts file that points to the server.

Here is stuff from the SQL Server Books:

To configure a Windows- or Windows NT-based client to use the Windows Sockets Net-Library, follow the steps under "Setting Up Server Connections," earlier in this chapter. In the DLL Name box, enter the appropriate Windows Socket Net-Library name. For Windows NT-based clients, select TCP/IP Sockets from the list. For Windows-based clients, type dbmssoc3 in the box.
The Connection String uses the format:
ip_address,[socket_number]
where ip_address is the IP address of the computer running SQL Server and socket_number is the optional socket number that SQL Server is listening on.
It is also possible to configure a Windows- or Windows NT-based client to use the Windows Sockets Net-Library by default. From the SQL Client Configuration Utility, in the Default Network box select TCP/IP Sockets. Using this method, connections can be established by using the ip_address,[socket_number] directly as the SQL Server name, or by using a server name with the format:
host_name,[socket_number]
where host_name is a TCP/IP host name that has been defined in the client HOSTS file or on a Domain Name Service (DNS), or is the machine name of a Windows NT Server running SQL Server if WINS is enabled, and socket_number is the optional socket number that SQL Server is listening on. For a client running Windows for Workgroups, the HOSTS file is located in the \WINDOWS directory by default. For a client running Windows NT, the HOSTS file is located in the \WINDOWS\SYSTEM32\DRIVERS\ETC directory by default. For other TCP/IP protocols that support Windows Sockets, see your TCP/IP documentation.
In all cases, if the socket_number is not specified, the Net-Library uses 1433, the official Internet Assigned Number Authority (IANA) socket number for Microsoft SQL Server.

Some additional Info on entering data in the advanced tab:

In the Server box, enter the name of the server. This is the name of the server you are using in DB-Library applications such as isql. The name does not need to match a network server name.
4. In the DLL Name box, select the name of the Net-Library (for example, Named Pipes) from the list.
Or you can type the name of a Net-Library DLL to use for the connection. (Do not type the ".DLL" filename extension.) Net-Library DLL choices are listed in "Setting the Default Net-Library," earlier in this chapter.
5. In the Connection String box, you can enter additional connection information as required. If no connection string is entered, the server name is used.
For information on the type of connection information that can be entered in this box for each Net-Library, see Network Client Connections.
6. Choose the Add/Modify button.
7. Choose the Done button.