M
Mark J. McGinty
[reposting as a cross-post to avoid multi-posting]
We've written an Outlook AddIn in VB6 that syncs with a SQL Server-based CRM
system. We're using Redemption, because... well, because it rocks! (Amongst
other reasons.)
Occasionally clients using Exchange Server get the following message, on the
line of code that assigns the Item property of a
Redemption.SafeAppointmentItem, SafeContactItem or SafeTaskItem:
"One or more items in the folder you synchronized do not match. To resolve
the conflicts, open the items, and then try this operation again."
Questions:
1. What causes these conflicts?
2. Is there a way to dispense with them programmatically
I have seen the Sync Issues\Conflicts folder in Outlook's UI, and some items
in it -- gotta say it isn't very intuitive; it isn't clear to me at all from
looking at one exactly what the nature of the conflict is, nor what options
are open for me. I would love to be able to force some of these to be
created, so I can test my code on a [virtual] test system, rather than
vicariously through the eyes of end users.
tia,
Mark
We've written an Outlook AddIn in VB6 that syncs with a SQL Server-based CRM
system. We're using Redemption, because... well, because it rocks! (Amongst
other reasons.)
Occasionally clients using Exchange Server get the following message, on the
line of code that assigns the Item property of a
Redemption.SafeAppointmentItem, SafeContactItem or SafeTaskItem:
"One or more items in the folder you synchronized do not match. To resolve
the conflicts, open the items, and then try this operation again."
Questions:
1. What causes these conflicts?
2. Is there a way to dispense with them programmatically
I have seen the Sync Issues\Conflicts folder in Outlook's UI, and some items
in it -- gotta say it isn't very intuitive; it isn't clear to me at all from
looking at one exactly what the nature of the conflict is, nor what options
are open for me. I would love to be able to force some of these to be
created, so I can test my code on a [virtual] test system, rather than
vicariously through the eyes of end users.
tia,
Mark