Yes, a vpn is the only way. Remember, using JET requites that you SEE the
file. Remember, you do NOT have to install jet where the file resides (ie on
the server). JET is running on YOUR END, and thus it simply needs to "see"
the file on the other end. The only way to share files across the net is to
use a vpn. JET cannot accept a socket connection since JET runs on YOUR end.
With a server based system like sql-server, you have the exact oppose setup,
where the "engine" runs on the server, and you connect to it. With a JET
file share, JET runs on your computer and OPENS the file on the other end.
Since JET needs to "open" the file, then JET has to be able to see the file
like any other regular file (exactly the same as word, or excel). You can't
use word across the internet either. There is nothing special about a mdb
file. It is just a regular file that windows wants to open. So, if you can
open the file remotely, then you can use it. Hence, that regular file can be
on your hard disk, or a network share, but for purposes, JET just thinks it
is a file, and want to open it. With sql server, you don't open the file on
the other end, but connect to some "engine" (some software running) that
accepts commands.
As mentioned, you don't install JET or anything where the file resides.
You can certainly setup some asp web pages that connects via JET to a mdb
file sitting on the server. It would then be the web server that is
accepting commands, and sending them to the JET file share on the same web
server. Of course, using asp pages with a web server does allow you to
connect to a JET mdb file share...but you are using ms-access anymore when
you do this (you are using JET...and a web server can connect to JET).
i can link access to the sql server tables via odbc so i
have the ms access
functionality and ease of use with sql server really collecting the data
from the website/perl
Yes, the above is correct. Further, if you make a web only application, then
as mentioned, you can use JET on the web server and not have to use
sql-server (but no ms-access front end can connect to that). You can however
certainly migrate your data out of the JET file share and into sql server.
You then can still thus keep your front end part in ms-access, and connect
to the server via ODBC. In that case, you can connect across the internet to
the database on the server with ms-access front end (and your users on the
LAN can also connect this way). Thus, when connecting to a sql database from
ms-access using ODBC, then you don't have actually see the files, and a
simple IP address will allow a socket connection.
This allows your ms-access application to function anywhere in the world and
connect to the server.
You can read my thoughts on using a VPN and ms-access at:
Using a wan with ms-access? How fast, how far?
http://www.attcanada.net/~kallal.msn/Wan/Wans.html
--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
ka****@msn.com http://www.attcanada.net/~kallal.msn 
