Type #1 would be handled by your existing code.
Type #2 are quite rare these days and could be handled with a last Else block. I'm not sure what object type they'd report. I haven't seen one in years.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
<(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> Hi
>
>
> I have a C# program that scans Outlook items using the Outlook API.
> To handle the different types of items I use a kind of switch:
>
>
> if (oItem is Outlook.DocumentItem) ...
> else if (oItem is Outlook.MailItem) ...
> else if (oItem is Outlook.AppointmentItem) ...
>
>
> The thing is I think I may be losing custom forms.
>
>
> I take it there may be two kinds of custom items:
> 1. Derived from basic types, for example IPM.Contact.Employee
> 2. 'All-Custom', for exmample, IPM.AntiVirus
>
>
> Is there a way to handle these by the Outlook API, or will I have to
> resort to using CDO/MAPI?
>
>
> Thanks
>