S
Steve
I have come across a new issue that appears to be as
inexplicable as previous memory management issues when not following the
design patterns of CDO's and CDONT's of .Net OOM programming. This one
involves only Recurring Meetings where in some environments when my code
accesses the item’s recurrence pattern and exception items if present
validates the excpetion is not a deleted exception and attempts to access the
Exceptions AppointmentItem, Outlook raises a dialog “Can’t read one instance
of this recurring appointment, Close any open appointments and try again or
recreate the appointmentâ€. I’ve searched the internet on this and found most
suggest a memory leak. This only happens with items defined as recurring
meetings and only if the user has entered a value into the recipient text box
and saved the item as my tests in my customer environment prove that neither
recurring appointment’s or recurring event’s exhibit this behavior. Finally
even though Outlook raises this warning - it still grants access to the
exception although Outlook may display more than one warning dialog per
exception. Also I've found if I delete all recipients from the series master
- no warning is displayed at all. Obviously this isn't a solution to delete
users recipient's.
Anyone have any ideas how to stop Outlook from raising the warning?
inexplicable as previous memory management issues when not following the
design patterns of CDO's and CDONT's of .Net OOM programming. This one
involves only Recurring Meetings where in some environments when my code
accesses the item’s recurrence pattern and exception items if present
validates the excpetion is not a deleted exception and attempts to access the
Exceptions AppointmentItem, Outlook raises a dialog “Can’t read one instance
of this recurring appointment, Close any open appointments and try again or
recreate the appointmentâ€. I’ve searched the internet on this and found most
suggest a memory leak. This only happens with items defined as recurring
meetings and only if the user has entered a value into the recipient text box
and saved the item as my tests in my customer environment prove that neither
recurring appointment’s or recurring event’s exhibit this behavior. Finally
even though Outlook raises this warning - it still grants access to the
exception although Outlook may display more than one warning dialog per
exception. Also I've found if I delete all recipients from the series master
- no warning is displayed at all. Obviously this isn't a solution to delete
users recipient's.
Anyone have any ideas how to stop Outlook from raising the warning?