Receive conflict check Error on Start up

[Sgt Gordon]

When I start up my database I receive a conflict check Box. I click on it to
resolve conflicts and it states that I do not have any conflicits. I do run
this database with a replicia that personnel use to enter data. I usually
only have one replicia and when I have problems I usually synchronize and
then delete the replicia and that usually fixes the problem. I have done
this this time and the problem continues. If there was a conflict and the
program does not show it how can I fix it. Please advise on how to stop
getting conflict checks when there are none.

 

[Arvin Meyer [MVP]]

You may want to take a look at the Microsoft Replication FAQ.

http://support.microsoft.com/default.aspx?scid=kb;en-us;182886

another good source for Replication information is David Fenton's site:

http://dfenton.com/DFA/Replication

 

[Sgt Gordon]

I removed all replicias from the database but I am still getting an error I
look at the FAQ and it stated to look at the MSysConflicts Table and this is
what it states (Reason
Recovered replicable data. This row was recovered from a corrupted
replicable database. Verify that the record contents are correct and then
reinsert the record, or delete this conflict record.) How do I find that
record so I can delete it or fix it?

 

[Arvin Meyer [MVP]]

You'll probably have to use a find duplicates query (excluding the GUID) to
find rows which have a conflict.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

 

[David W. Fenton]

what it states (Reason
Recovered replicable data. This row was recovered from a corrupted
replicable database. Verify that the record contents are correct
and then reinsert the record, or delete this conflict record.)
How do I find that record so I can delete it or fix it?

The conflict record should have the GUID of the table and record.
You need to figure out which table is involved and then look at the
record with the matching GUID. It may be in a different replica, so
you may also need to look at the other replica (assuming you haven't
deleted it -- you can't create and delete replicas willy-nilly
without running the danger of ultimately completely hosing your
replica set). On the other hand, you could just try appending the
data in the conflict record to the corresponding table and seeing if
it raises and validation errors.

You need to stop promiscuosly creating and deleting replicas, or
you're bound to continue to have major problems down the road.
Indeed, I would say that the problem you're experiencing is likely
due directly to that mistake.