RE: How to handle conflicts?
- From: v-mingqc@xxxxxxxxxxxxxxxxxxxx (Michael Cheng [MSFT])
- Date: Tue, 03 May 2005 06:08:43 GMT
Hi Danny,
Welcome to use MSDN Managed Newsgroup!
Additionally to David's perfect explaination, I would like to excerpt some
answers from KB Q282977 for your reference
===================
- Why do I get a conflict when I synchronize my replicas?
Because more than one replica has updated data in the same record (in the
same column of the same record if you have chosen column-level tracking)
since the last synchronization. Since Access 2000/Jet 4.0 treats data
errors in the same manner that it treats conflicts, other causes could
include violations to the primary key constrictions and newly created
validation rules.
- How can I avoid (or at least minimize) data conflicts?
The best way to minimize conflicts is to keep them from happening in the
first place. An entire book could be written on this topic, but here are a
few examples of ways to avoid or minimize conflicts:
1. Adding new records instead of editing existing ones. For example, when
tracking inventory, rather than keeping a single field that has the
quantity, create a log table that lists the change. This way, when two
different people remove some of the same item, you will not get a conflict
for the two of them editing the same row.
2. Creating smarter synchronization schedules. The general rule is to set
up your synchronization schedule based on the way your application works.
If one replica contains data that another one will need right away, your
application should make the synchronization right away. This avoids
potential conflicts with someone else changing the same record before the
first set of changes has propagated. It will also help you avoid angry
customers who wonder why they just gave someone an address change and why
they have to do it all over again for someone else!
- How does Microsoft Access resolve synchronization conflicts?
In earlier versions, synchronization conflicts were resolved based upon an
algorithm whereby the most often changed copy of a record won. This
algorithm worked, but was unsophisticated and confusing.
Microsoft Jet 4.0 introduces an algorithm whereby replicas in a replica set
are assigned priorities and the highest priority replica wins in the case
of a synchronization conflict. Where priorities are equal, the replica with
the lowest replica ID wins.
Note: The priority-based conflict-resolution algorithm will work in
conjunction with the corresponding Microsoft SQL Server capability when
Microsoft Jet and Microsoft SQL Server replication are used together.
Replicas are assigned a priority, a real number between 0 and 100,
inclusive, when the replica is created. At the time a database is made
replicable, the Design Master's priority is set to 90. The default priority
of additional replicas is 90 percent of the parent replica's priority. You
can easily specify another priority value either by using the Create
Replica dialog box in Access or by using the CreateReplica method in JRO.
Users must have dbAdminister privileges in order to specify that the
priority of a replica be greater than the priority of the replica from
which it is being created. Using the file system to make a copy of a
replica will create a replica with the same properties and priority as the
source replica.
Note: All replicas upgraded from an earlier version of Microsoft Jet are
given an identical priority value of 90. Replicas created through the
MakeReplica method in DAO have a default priority equal to 90 percent of
the parent replica's priority.
===================
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- References:
- How to handle conflicts?
- From: Danny J. Lesandrini
- How to handle conflicts?
- Prev by Date: RE: DAO or JRO, that is the question
- Next by Date: Re: What to do with disconnected laptop?
- Previous by thread: Re: How to handle conflicts?
- Next by thread: Compact twice before synchronize?
- Index(es):
Relevant Pages
|
