I have a split database running under Access 2003 which uses a programmatic
sync. This database has been running for several years, with sync both ways
working fine.
Now, as the world turns, I'm testing it with the released Vista and Office

I have a small Access database with 1 parent, and 10 child records. I
know that I want a configuration with 2-way synchronization. There will
be updates done at the main office and by people on the road who will
synch up daily.

I have replicas that I want to move to another machine and am uncertain
how to do this.  Here is my configuration.  I have the master and a
full replica on machine A (the server).  I have two partial replicas
that use indirect replication over the internet each on machines B & C

As far as I understand from my readings (3 days) remote server needs to
have a synchronizer either with internet or indirect synchronization.
I can't really understand why don't we just have dropboxes (with UNC
paths) on the remote server (RemSrv) and each synchronizers running

Is there a way to test if a replica has lost its replication.  The loss
of the replication doesn't mean that the ReplicaID disappears does it?

In another thread that is getting very long, jacksonmacd suggested a
method for using indirect synchronization in a scenario where remote
PCs have synchronizers but the server does not.
OK. Let's pursue that suggestion.  General setup:  Four LANs that are

Because the original design master (which I did not make) was no longer
valid, I made a replica of the database replica that was in current use
and had up to date data.  I set the new replica as design master and
made the needed change to its design.  Now I would like to synchronize

Is there a way to tell if two replicas need to be synced without
actually starting the direct synchronization process.   At this point
in time, indirect synchronization is not an option.
Thanks.

Here's the situation;
1) Not allowed to install Jet Synchronizer on server, but can install
it on remote PCs.
2) Can't add a desktop to the LAN to handle synchronization in lieu of

I'm having trouble opening the Conflict Resolver using Shell and
switches.
I'm getting an invalid switch error.  In code the first switch I have
is Login.  Other than that I'm following the switches exactly as shown

I'm concerned that two remote users may simultaneously try to sync with
a hub replica on the server.  I know that Access will generate an error
but I'd like to prevent possible conflicts from attempted simultaneous
syncing or worse corruption before it even has a chance to get ...

What are the limitations on "storing the design master in a safe
place"?
Specifically, can I keep the design master "off-ste", which means that
while off-site it cannot be synced.  Then when changes are made, place

David;
In another post on hub corruption over a relatively slow connection you
noted:

I'm still learning about replication and am playing around with it.
Here's the scenario.  I have a hub replica, a laptop replica and a
desktop replica.
1) On the laptop replica, I deleted 130,000+ rows from a back-end

Before I make the leap to include replication, I need a plan for what
happens if the hub replica (located on a server) in a star topography
gets corrupted.  I'm only talking about back-end files (i.e. only
tables).