Hi all

I was directly synchronising two members of a replica set
over a VPN with ADSL connection when I think the
connection timed out. I have since copied the remote
database onto a local desktop and tried to open it.  There
was an error in opening the database but Access was able
to repair it.  I then synchronised the repaired copy with
the original local replica and all went well except that
the conflict viewer indicated there was a synchronise
conflict.  

When I go to view the conflict, the viewer says <No
conflict Tables>. This occurs for both the replica I
synced from and the one I synced to, and propogates to any
other replica in the replica set with which I synchronise.

If I deliberatly make a conflict for two replicas and then
synchronise It still flags the conflict and deals with it
corectly but thereafter the problem with flagging bogus
conflicts persists!

If anyone has any ideas or has experienced this before
please let me know.

Regards

Col