>>Yes, if it's not on the SQL Server you'll need to give the user access to the network. I don't think there's a way to have the ODBC driver dial the network. You can either have the user dial in manually using dial up networking or you could have your application use dial-up networking to connect before it tried to access the remote data. I think there are some classes in the file section here to make calls using DUN. If not, take a look at Rick Strahl's wwipstuff. It's free from www.west-wind.com.
>
>Thanks again. I will check out those resources.

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