> I have a front end/back end database that needs to be used/updated
> at three locations, none of which can access each electronically.
If there's never any possibility of any connection between the
sites, then there is no way you can ever use Jet replication.
Period.
End of statement.
On the other hand, if you can occasionally connect via the Internet,
or if one machine is a laptop and is carried into the various
offices occasionally, then replication is possible.
But if not, then you can't use Jet replication.
> I need to ensure
> that the changes in all three locations plus changes made to the
[quoted text clipped - 10 lines]
> forum and have decided that replication is a better way to go.
> I'm just not sure on how to achieve it.
If you can't connect, then it won't work.
But since there is Internet access of some sort (otherwise there
wouldn't be any email), then it's possible to set up indirect
replication.
> Because the changes are coming from different locations, I'm not
> quite sure how to set this up. If it was only one location, I
> assume I would start by sending them a replica. then sending them
> a copy of the master periodically which they could sync and send
> back to me.
No, absolutely not.
You send them the replica at the beginning, yes, but from then on,
you never send a replica ever again. At that point you have to synch
them in place. You do this with the synchronizer and with the
Internet, the easiest way to do that is over a VPN.
> I get lost when trying to figure
> this out with more than one location as well, if I send a copy of
> the master to each location, how do I get those changes into my
> original? Can I make changes to my original while these copies
> are out?
You have to use indirect replication. Re-read the white paper and
FAQ on that subject and then come back with questions on what you
don't understand.

Signature
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/