It seems you may be splitting hairs a bit - ?
There is no such thing as "Access Replication," because Access is a database application development tool, and not a database. It provides a default database engine (Jet), and the choices on the menu to replicate are just links to Jet functionality.
It's not splitting hairs to maintain this distinction, especially in the context of a discussion of using a Web server, where Access is simply not involved (only Jet).
Reads like the following are what I based my suggestion on:
Link
That's a very lame article, seems to me. It doesn't discuss any of the real issues involved, nor allude to any of the many precautions you need to take when replicating (it doesn't even mention replicating only data tables).
Seeing as how he wants to work with data in the field then sync it back up with a master, I thought it a reasonable option to consider...?
I don't see *anywhere* that there's any need to synch back and forth. All I saw was this:
...is there a simple way of exporting and importing the access data on the webserver again...
Doesn't look like synching to me.
(granted it doesn't look like something you want to do over a slow internet connection)
It works fine if you use indirect (or Internet) replication. But those are very complex to implement and require components running on the server side.
The Jet Replication Wiki has information on all of these issues:
http://dfenton.com/DFA/Replication/