B
Ben
Hello,
I have the following problem:
The initial situation: A program I made can export appointments to
Outlook via the OLE interface. The exported appointments get an
addtional property so that I can distinguish the user-created
appointments from the exported ones.
Through my program the user can also delete all the previously exported
appointments.
This does seem to work, i.e. the appointments don't show up anymore in
Outlook, but, and that's the problem, in the calender the days with
appointments are still shown bold, and if I try to create a new
appointment that overlaps with the previous appointment (that should
now be deleted) I get the message that the new appointment overlaps
with an existing one - the previous one that somehow didn't get deleted
completely.
To get the appointments that should be removed I do an Items.Restrict
(where Items is the list of all appointments) with the appropriate
filter expression. Then I simply do a for loop and delete the item at
index 1 (with RestrictedItems.Remove(1)) until all items are deleted.
I don't know if it's a problem with my code or with Outlook as my code
isn't particularly complicated.
I have the following problem:
The initial situation: A program I made can export appointments to
Outlook via the OLE interface. The exported appointments get an
addtional property so that I can distinguish the user-created
appointments from the exported ones.
Through my program the user can also delete all the previously exported
appointments.
This does seem to work, i.e. the appointments don't show up anymore in
Outlook, but, and that's the problem, in the calender the days with
appointments are still shown bold, and if I try to create a new
appointment that overlaps with the previous appointment (that should
now be deleted) I get the message that the new appointment overlaps
with an existing one - the previous one that somehow didn't get deleted
completely.
To get the appointments that should be removed I do an Items.Restrict
(where Items is the list of all appointments) with the appropriate
filter expression. Then I simply do a for loop and delete the item at
index 1 (with RestrictedItems.Remove(1)) until all items are deleted.
I don't know if it's a problem with my code or with Outlook as my code
isn't particularly complicated.