Close method returning 80040108

[Michael Tissington]

I'm using C++ and Outlook 2007. In my Addin I'm calling the Close method
with olDiscard on a Contact Item.

I can get various properties on the item but when I try to do a Close I get
back an error 0x80040108 which I think is invalid Object.

This works in previous versions of Outlook.

Any ideas please ?

 

[Wei Lu [MSFT]]

Hello Michael,

I have noticed we just resolved your issue "OnAction callback
IRibbonControl C++" which include the same error message you mentioned.

Did this issue related with the previous issue?

Are you using ATL to develop the solution? What's the sample code?

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Ken Slovak - [MVP - Outlook]]

Where are you calling Close? Outlook 2007 and the latest hot fix for Outlook
2003 change the old behavior to return an error if you try to close an
Inspector or item in the item.Close or Inspector.Close event handlers.

 

[Michael Tissington]

Thanks - but its not related

This issue happens with either early or late binding.

 

[Michael Tissington]

Thanks and Argh .... Yes, I'm calling it in the Close ... basically I do not
want the Outlook confimration dialog box to show up - I've already displayed
my own.

Is there another way to do this now ?

 

[Ken Slovak - [MVP - Outlook]]

Argh yes, since they broke compatibility.

It's documented as a known issue for Outlook 2007 at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;929593, not
documented at all for the change to Outlook 2003.

I've been using timers for my applications, but where I start the timer
depends on if I'm handling Item.Send or whatever. Otherwise I don't know of
any workarounds.

 

[Michael Tissington]

Thanks for the idea - I'll post back if I come up with a better workaround
....