We use custom fields in Outlook (user properties)
One of these is called ScanID which is Integer data type.
We use both Outlook 2003 and Outlook 2007.
For the Outlook 2007 VSTO project, the below line works fine
ForOutlook 2003, the interop assembly doesn't seem to have olInteger property. I can use olNumber as data type but then that causes an error such as:
"A custom field with this name but a different data type already exists. Enter a different name."
I know Outlook 2003 supports this data type because I can add a new field using Outlook's GUI and specify Integer. Why doesn't it recognise it in VSTO?