> Hi
>
[quoted text clipped - 28 lines]
>>
>> Bob
Try to manually sync with each member of the replica set.
You could also Google search for cannot open resolve conflict menu
Bob
John - 17 Jan 2008 19:59 GMT
How do you manually sync? I tried Tools->Replication->Resolve Conflicts
menu, is there another way?
Regards
>> Hi
>>
[quoted text clipped - 36 lines]
>
> Bob
user@domain.invalid - 17 Jan 2008 23:15 GMT
YOu do this by Tools - replication - Synchronize now
Bob
> How do you manually sync? I tried Tools->Replication->Resolve Conflicts
> menu, is there another way?
[quoted text clipped - 41 lines]
>>
>> Bob
John - 17 Jan 2008 20:03 GMT
Google search for cannot open resolve conflict menu brings nothing at least
on first few pages
>> Hi
>>
[quoted text clipped - 36 lines]
>
> Bob
user@domain.invalid - 17 Jan 2008 23:22 GMT
> Google search for cannot open resolve conflict menu brings nothing at least
> on first few pages
[quoted text clipped - 39 lines]
>>
>> Bob
Why not try to respove conflicts in one of the replicas. Perhaps also
try on another PC.
Bob
> The problem is that when I open the replica db I get the message
> "This member of the replica set has conflicts from synchronizing
[quoted text clipped - 4 lines]
> remains and gives message every time db is opened. I have tried
> doing a detect and repair on Access 2000 but no luck. Any ideas?
Make sure you've got hidden objects and system objects displayed
(Tools | Options), and then check the MSysConflicts table. If it has
no records in it, then you don't actually have any conflicts. If it
*does* have conflicts, you'll need to decipher it by looking up the
GUIDs of the tables involved. You should also check to see if there
are conflict tables for any of your user tables. If you have a table
called tblPerson and there's a conflict, there will be a table
called tblPerson_Conflicts. That will have the data for the *losing*
record in the conflict. If the winning record is OK, then you can
just delete that table (or check all the records there before
deleting it).
Remember, the conflict resolver does nothing but offer an
opportunity to check that Jet resolved the conflicts correctly --
the conflicts have already been resolved. So, if worst comes to
worst, you can just delete the conflict tables and be done with it.
You should also try looking at other replicas, which may allow you
to resolve the conflicts.
Another thing you might try is to open the conflict resolver
directly and then open the replica you want to look at. The default
location for the conflict resolver is:
C:\Program Files\Common Files\Microsoft Shared\Database Replication
and the conflict resolver is called WZCNFLCT.EXE.
If you run it, you'll get the opportunity to point it at a
particular MDB.
Report back to us on what you find and then we can go from there.

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