Like Dan said your best bet is to use terminal server
services or something similar, not connect to the
database, but use a local PC remotely.
Because both with ODBC or VFP OLEDB Provider you
need to give a path valid in the current LAN, there
is no Server process running for a DBC, it's a file
database.
You can solve that by using a VPN connection, but that
is not only slower, but also has a higher latency
compared to a LAN, remoting the desktop can handle
this better in most cases, then remoting the data
access. Be aware that DBFs are sensitive to network
errors or unstabilities and these are more probable
in a VPN network.
There once was a product called VFP Server, but their
site www.vfpserver.com is down. They provided the
missing service that would enable using DBCs remote
as a real database server, but using that would need
a rewrite of the applications data access anyway,
and if you choose a rewrite MS SQL or some other RDBMS
may be the better choice, than adding a Server component
to a DBC.
A third possibility is another way of a rewrite, keeping
the DBC, but developing a web application frontend for it.
Bye, Olaf.