Replication Conflict Viewer crashes

Replication Conflict Viewer crashes

Post by bruc » Fri, 21 May 2004 01:22:51


Hello,

I'm getting rather frequent crashes from the Access 2003 replication
conflict viewer. I recently synchronized two Access 2000 format
databases from Access 2003. During this synchronization, a design
change was propagated from one database to the other (a field was
added to a table, affecting a large number of records requiring me to
significantly increase the default MaxLocksPerFile registry entry for
Jet 4.0). There was also data synchronized in addition to the design
change. The data synchronization incurred some data conflicts. I
opened the Access 2003 replication conflict viewer on one of the
replicas and was able to view the first few fields of each conflicting
record, but if I attempted to scroll through the conflicting fields
using the scroll bar on the right side of the window, the viewer would
crash with a dialog box saying "run time error 340, control array
element '56' does not exist", followed by a "run time error 440,
automation error" dialog. Does this indicate database corruption?
Also, if I make a design change in the design master, do I need to
then synchronize each replica directly with the design master to
propagate the change, or can I synchronize the design master with the
hub and then synchronize the hub with the other replicas in the set?
Thanks,

Bruce
 
 
 

Replication Conflict Viewer crashes

Post by mich » Fri, 21 May 2004 04:58:08

"Bruce" < XXXX@XXXXX.COM > wrote...


How many conflicts?


How many fields in the table?


Not that I know of -- but then I have never heard report of this, even back
when I was the dev owner of the viewer.


You can synchronize any replica. I doubt the design change has anything to
do with the error, fwiw.


--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.

 
 
 

Replication Conflict Viewer crashes

Post by bruc » Sat, 22 May 2004 00:06:36


The times I have seen this happen the number of conflicts has been
small...always less than 10.


There are 172 fields in the table. The option to show only the
conflicting fields is selected.

Bruce
 
 
 

Replication Conflict Viewer crashes

Post by mich » Sat, 22 May 2004 01:27:25

"Bruce" < XXXX@XXXXX.COM > wrote...


This would be the main source of there being a problem. Which is not to say
it wouldn't still be a bug. But the bulk of the testing was done on much
more reasonably sized (and often properly normalized) schemas.


Note that this means the viewer has to load every item and compare them to
see if they are the same or not. Depending on the complexity of the fields
and the amount of change, the time it takes to "compare every item and
display the changed ones" vs. "display every item" can vary in terms of
which is more intensive.

My advice would be to do some schema design, specifically to properly
normalize the data, as a design that is so far from 3NF as to have tables
with 172 columns in them is fraught with either unnecessary duplication,
wasted space, and/or data inconsistencies which replication will only be
hurt by.


--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.