Developer Forum

I'm relatively new to replication in Access DBs, and have run into a problem
I haven't been able to quickly solve.

In moving data around, and re-designating the Design Master as a design
master after having moved data, I've ended up with lists of old replicas
(paths to them, actually) in the pick list when I go to
Tools>Replication>Synchronize Now, under "Synchronize directly with
replica."

A reference I've got says that I can attempt to synchronize with the (no
longer existing) files at these paths, be notified with a warning that they
don't exist, and upon reopening the DM the next time, those records will be
gone from the picklist.

It's not working, unfortunately ... the records are still there upon
restart. I'd like to get this cleaned up, but am not sure where to go next.
I can see records for these paths in table MSysReplicas, but can't edit that
table -- not that I'd know what I was doing if I could.

Thanks for any suggestions of solutions/workarounds that you may have.

-- Eric Johnson

"Eric Johnson" < XXXX@XXXXX.COM > wrote in



That's the correct method, but it leaves out the final steps of the
process.


After you've synched from the DM with all the dead replicas, you
then need to synch around your full replica set. You may also need
to attempt a synch with the dead replicas from every one of the live
replicas.

It can be done -- I've done it.

But it's not as simple as doing it from one replica. You have to
purge the entries from the MSysReplicas table in all the replicas
before it will all go away.

And, yes, there's a bit of voodoo to this explanation, as sometimes
you don't have to do the whole process, and sometimes you do.

Keep in mind also that a single replica path/filename in the
dropdown list can represent an infinite number of unique replica IDs
that were possessed by MDBs at that location with that name. So, you
could see one item in the dropdown list, but it could represent
dozens of replicas in the MSysReplicas table. You have to attempt
the synch with the dead replica as many times as there are unique
ReplicaIDs listed at that location in MSysReplicas.

And, of course, this is why it's such an incredibly bad idea to move
or copy or rename replicas after they are already in use.

--
David W. Fenton http://www.yqcomputer.com/
usenet at dfenton dot com http://www.yqcomputer.com/