Bob,

yes, what you write will work and I use that all the time too - BUT, it's a bit of "cheat" in this case. Remember that I want to do this through the ODBC driver with the end result being that I wind up doing it [through an ODBC driver] from the Unix box. Mapping a drive letter works in the Windows case of course, but doesn't translate to Unix. And yes, By Jove!, I *never* work without a firewall but it's easy enough to set the rules to allow that traffic through.

I think you're right that there's no other easy way to do this...

thanks,

-Arne


>>
>>Let's take another, simpler example. Suppose *you* have a Win2K box with a VFP database on it (forget Unix for a minute). How can *I* specify a DSN using the VFP ODBC driver that gives me access to your d/b via an Internet connection? And NOT using a VPN. I can't figure out any way to do this. If your machine is on my local area net, it's easy using Windows domain/server/share notation to specify th VFP ODBC Driver's Data Source Path. But when all I have is your IP address I'm hooped (aren't I??).
>
>That depends on your own security issues. and how your firewall is set up. if you have a fire wall.
>
>If you mark the folder which holds the dbc/dbf's as shared, then the other windows machine can hit it, provided you have a static ip address for that machine, and that IP address is sitting on the internet.
>
>the accessablity is based on NT user name password.
>
>then once you can hit it,
>from the command line in windows just do a \\216.xxx.xxx.xx if its found, then it prompts you for a username and password. once you are connected. then map the drive, and set up your dsn.
>
>I do this all the time, over the internet, but then again I have static ip's at home at my office, and my firewall only allows in requests from MY home static ip's
>
>sure its not quite setting up a vpn. but it is secure.(not encryped however).
>
>but thats about the only way I can think of doing what you are looking for.
>