Help with Replication Scenario

[Guest]

I have a front end/back end database that needs to be used/updated at three
locations, none of which can access each electronically. I need to ensure
that the changes in all three locations plus changes made to the master at my
location are in sync.

I have the master copy and have been sending out copies of it via e-mail or
FTP to the other locations. The make their changes, and send it back to me
and I manually update the master using VB to find changes. Certainly not the
most efficient way.

I've read the replication white papers and various posts on this forum and
have decided that replication is a better way to go. I'm just not sure on
how to achieve it.

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. 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?

Any suggestions on how to achieve my goal would be greatly appreciated.

 

[Douglas J. Steele]

You might consider posting this to the Replication newsgroup
http://msdn.microsoft.com/newsgroup...osoft.public.access.replication&lang=en&cr=US

 

[Guest]

Done,

I knew there used to be a replication newsgroup, just couldn't find it.