You have to setup RAS on the incoming machine so that it's waiting
for the phone to ring and will pick up when it does. Then you have
to set up a simple dialup networking connection on the remote
machine. You can execute a dialup networking connectoid by using
Shell() to call RunDLL and calling the name of the connectoid (which
is case-sensitive, unlike just about everything else in Windows). If
you search Google Groups on RunDLL and dialup networking (and maybe
connectoid) you'll find instructions. I know I've posted such
instructions in the past in comp.databases.ms-access, though I've
never used it with NT-based versions of Windows.

Once you're connected, then you have a standard SMB networking
connection and the synchronizer on one machine should be able to see
the dropbox on the other machine (and vice versa). At that point,
you should be able to initiate the synch.

One thing you might do is a loop with Dir() command looking for the
remote dropbox path, and once it's found, that means your connection
is up and ready to synch.

It's not a function of the size of the database but of the amount of
changes you've made to your data. I've done it over 28.8 and
single-channel ISDN (64K) and a database that was being regularly
used by a dozen users in two offices never took over 10 minutes to
synch -- indirect replication is *very* efficient.

Of course, the more often you synch, the more efficient it is, since
it has fewer generations of changes to synchronize.

There's not much in the way of documentation for Jet replication
anywhere. This newsgroup is it.