Hi guys,
We've noticed an issue with EasySync and was wondering how MirrorSync addresses this scenario. Basically, as you probably know, EasySync gathers data by looping through the tables. The issue is that during that loop, another client can push data. So, the original client will pull records potentially that are orphans (since it's already pulled from a parent).
If that makes any sense at all, can you address how MirrorSync avoids what I've been told is called "Collision Detection."
tia,
Barbara