Re: Conflict Tables

Tech-Archive recommends: Fix windows errors by optimizing your registry

Mike <iatros56@xxxxxxxxxxx> wrote in
news:1183060375.088340.71430@xxxxxxxxxxxxxxxxxxxxxxxxxxx:

Well, we've gone through all the replicas (35 computers - 3
replicas on each) and actually direct synced each one of them with
the Design Master (I was desperate!!). The two Msys conflict
tabes remain. In fact, over the past week we have had a couple of
replicas "unreplicate" themselves during the daily compact routine
and about 12 that became corrupt.

The loss of replication is a sign that the replica was corrupted.

So, I think we need to unreplicate and re-
replicate the Design Master and start from scratch. This was not
a light decision. This takes down the entire company for a few
hours (we're a 24/7 medical company) and we'll have to download
the new replica (500 MB) to the remote sites (about 30 of the 35
computers). We're starting Saturday.

How could corruption develop in your replicas? That's the key
question, seems to me.

For what it's worth, I've been doing replication since 1997, and
have not once seen the problem you've encountered.

I've seen corruption that resulted in loss of replication, but never
the error you reported.

We are using the Microsoft Replication Conflict Viewer and I am
thinking about adding my own conflict resolver. However, I have a
question. Jet 4.0 is new to me - as we have been using Access 97
until just recently.

Hold on a moment. Was the problem you had in a Jet 3.5 replica set?
Did I know that when I replied earlier?

With Microsoft's Conflict Viewer, If a conflict
occurs on my computer and I clear it does my choice propagate
throughout the topology and clear on all 35 computers, or does the
conflict have to be cleared on each and every computer? I'd like
to be able to have all conflicts "centrally" located and reviewed
and cleared through one person.

Jet 4 added two major replication features:

1. universal reporting and resolution of all conflicts, AND

2. field-level conflict resolution.

Moving to Jet 4 might eliminate the vast majority of your conflicts
in the first place, but it would also make it much easier to resolve
them, particular if you have a star topology, where one or two hub
replicas are synching with all the remote replicas.

All that said, you should really pin down what caused the corruption
in the first place (i.e., figure out which replicas were corrupt)
and the fix whatever was causing it, or you may be back where you
started.

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

Relevant Pages

  • Re: Conflict Tables
    ... we've gone through all the replicas (35 computers - 3 replicas ... Master. ... The two Msys conflict tabes remain. ...
    (microsoft.public.access.replication)
  • Re: 3167 error - record is deleted in replicated database
    ... sync to the server. ... you open these replicas? ... No error messages in conflict viewer. ...
    (microsoft.public.access.replication)
  • Conflict resolution
    ... The database I built uses 3 or 4 full replicas to sync with another replica which I then sync with the design master. ... Gen_TempField*0 is also an Access added field but I don't know what it's doing and I don't know why it wants me to resolve the conflict if it created the conflict. ...
    (microsoft.public.access.replication)
  • Conflicts dialog box
    ... I couldn't view conflict. ... The conflict dialog box keeps popup in design master and ... also replicas. ...
    (microsoft.public.access.replication)
  • Re: Intermittant 3167 error/indexing problem
    ... That thread clearly points to corruption as the problem. ... with other replicas, but there is something internally screwed up. ... I can now answer some of the questions above re the network ... I have created a brand new set of data, design master and replicas. ...
    (microsoft.public.access.replication)