A
Andreas Walkenhorst
Hi out there,
I have to save some data from appointmentitems from outlook to
MS-SQL-Server (by an addin). This usually works without problems, but
now I ran into a problem where I do not have any idea of how to solve
it:
The user has done the following things:
1 - Created a recurring appointmentitem (correctly saved to sql
server)
2 - Changed some items / created exceptions (correctly saved ...)
3 - Changed the whole recurring appointment and by that killed all
exceptions (correctly saved...)
If he now again wants to change an Item / create exceptions he fails
The reason is clear, as - when the records in the database are created
- I save the startdate in a field called originaldate (which is the
same thing that outlook does when exceptions are created)
But when the user kills the exceptions (3), the originaldate in
Outlook will be different from that in the database when he creates
exceptions for the second time. By that I am not able to address the
record in the database correctly, as I use entryid + originaldate as
primary key in the database.
I thought that I could check for recurrencepattern.regenerate, but
that method only seems to woks for taskitems, but not for
appointmentitems.
Anybody out there who has any idea how to solve the problem without
killing all records in the database when changing recurring
appointmentitems?
Andreas
I have to save some data from appointmentitems from outlook to
MS-SQL-Server (by an addin). This usually works without problems, but
now I ran into a problem where I do not have any idea of how to solve
it:
The user has done the following things:
1 - Created a recurring appointmentitem (correctly saved to sql
server)
2 - Changed some items / created exceptions (correctly saved ...)
3 - Changed the whole recurring appointment and by that killed all
exceptions (correctly saved...)
If he now again wants to change an Item / create exceptions he fails
The reason is clear, as - when the records in the database are created
- I save the startdate in a field called originaldate (which is the
same thing that outlook does when exceptions are created)
But when the user kills the exceptions (3), the originaldate in
Outlook will be different from that in the database when he creates
exceptions for the second time. By that I am not able to address the
record in the database correctly, as I use entryid + originaldate as
primary key in the database.
I thought that I could check for recurrencepattern.regenerate, but
that method only seems to woks for taskitems, but not for
appointmentitems.
Anybody out there who has any idea how to solve the problem without
killing all records in the database when changing recurring
appointmentitems?
Andreas