Synchronize Problem

[SteveE]

I have a Access2k database where the backend data file is Replicated, all was working fine with synchronizing until a couple of records were deleted. Now I get the "Synchronization was completed successfully" message after running but then I get "This member of the replica set has conflicts from synchronizing changes with other members." "Do you want to resolve conflicts now?"

When trying to resolve the conflicts there is no ***Conflict table, if I check the MSysConflicts table I can see 2 records from my "Contacts" table which were deleted causing the issue, but I cannot work out how to resolve these,

I have checked all the replicas and they all show the same as above. Could anyone advise how I can resolve this ?
Any help / advise will be appriciated.

Steve

 

[dfenton]

Starting with Jet 4, all replicas report all conflicts (which means any conflict can be resolved at any replica, as opposed to in Jet 3.x, where you could only resolve the conflict in the replica in which it happened).

A record delete problem probably indicates a referential integrity problem. You should supply the full error message in the MSysConflicts table for it. Also, that will tell you the source replica, which may or may not have data that is different from the other replicas (it depends entirely on the exact error caused by the delete, e.g., delete in one replica not propagated to other replicas because of RI failure, or a different kind of delete problem).

You have to read the data in the MSysReplicas table and decypher it. This means dealing with the GUIDs for the tables involved and the replicas involved and figuring out which records are causing the problem.

And once you fix it, you should look at your application and figure out if you can prevent this kind of error from happening. As an example, CASCADE DELETES should be off in replicated databases, because it can cause data errors like this to multiply exponentially. And perhaps you have an error in the design of your schema, or business rules that are not going to work well with the way Jet handles synchronizing deletions. In that case, you might need to flag deleted records instead of actually deleting them, and then hide them from users in your application's front end.

 

[SteveE]

David,
Many thanks for your reply, I will ensure the cascade delete is off when I am back in work. Just so others who may be reading this post are aware I think I have now managed to resolve this present issue. I tried to sync from a laptop which has 2007, and yes it reported the conflicts BUT it allowed me to use its conflict manager and resolve them. I "think" maybe the problem was created on a laptop using 2007.
Thanks again for your help and advise , appriciated

Steve