>>You'll need RAS running somewhere on your network, it doesn't have to be on the SQL Server. Once the user connects via RAS he or she is connected to your network just like anyone on the LAN (except that the connection is much slower, of course). The user can then connect to SQL Server just like anyone on the LAN does.
>
>Thanks.
>
>A couple more questions:
>
>Obviously when I set up RAS, if it is not on the SQL Server, I need to allow access to the entire network instead of just the computer running RAS, right?
>
>How do I set up the ODBC entry so that it knows to dial out to find the server? Or am I missing something yet?
>
>TIA


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.