First, I don't know much about this at all (I just created my first DSN last week :) so....

Can't you create the dsn and use a fixed IP and path to point to the data.
ex:
\\255.255.255.255\\SomeFolder\SomeData.dbc

I just tried and I can point to a VFP .dbc on my LAN that way. If your ISP gives you a fixed IP and you know the path I would think that would work. You don't need a drive letter, I use the unc on my lan and it's seems to work fine (\\ServerName\Folder\Data.dbc)

Again, I know little about it so I could be completely offbase.

>> Actually, it does (indirectly). It doesn't matter if it's a LAN connection or a dial-up. Most ODBC drivers are strictly drive mapped. They're not client-server (although the SQL Server ODBC is). If the backend database is a C/S database, yes, you can use the ODBC drive to access it. If it's not, then no you can't. If your ISP is willing to give you an NT account and a shared network drive, then you will be able to use ODBC to access it. Once you're connected to the ISP, you map a drive letter just like you can do over a LAN. But, it's going to be slow.
>
>Thanks everyone, I looked at the west-wind site, some interesting stuff. Unfortunately I don't have the time right now to do web development so I was looking for a shortcut.