It is certainly possible to split the database and put the back end on an
Internet site. An internet connection is, unfortunately, just not fast
enough for a multiuser configuration for a file-server database such as Jet.

You can write .asp or ASP.NET pages to allow access from user's browser. But
you will not be able to use the Access front-end with the back-end on the
Internet.

Closest thing would be Access' Data Access Pages, but those are limited
(users must have Internet Explorer 5.5 or later, etc.) so that they are
mostly used in intranets where there is close control over the users'
software. With DAPs, the users access the application on the server via
their browser.

Another possibility, for relatively simple databases, is Microsoft Front
Page with the Data Interaction Wizard. Again, the users access the
application via their browser... it is a "thin-client" solution, not a
"rich-client" solution like the Access front-end.

  Larry Linson
  Microsoft Access MVP

You could put the back end on a server, but you would have to setup
networking from your computer to that server. And, going across the internet
is too slow. You can read about the problems of doing the above here:

http://www.attcanada.net/~kallal.msn/Wan/Wans.html

You can access the backend by mapping to the site.  It's
risky for the Internet site because it will have to share
the folder but if they are willing you can map a drive to
the \\tcp/ip\sharefolder then link to the map drive