Wait until "COM environment" is ready

[water]

Wooltown and I "brush up" the Outlook UDF.

Now I've noticed a strange difference between Outlook 2002 (the one running in my office till a few days ago) and Outlook 2010 (the one running now in my office on Windows 7).

If I opened Outlook using ObjCreate when Outlook wasn't running yet and immediately accessed a property in Outlook 2002 it was working fine.

With Outlook 2010 I get Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT)). If I Sleep() for a few seconds everything works fine again.

So I get the impression that Outlook now does some of its startup asynchroniously. I've searched the internet high and low but couldn't find a single hint.

Am I doing something wrong? Is there a way to check if Outlook has finished starting up so the "COM environment" is ready to use?

Thanks for any support!

Edited March 20, 2011 by water

[flyingboz]

Is there a way to check if Outlook has finished starting up so the "COM environment" is ready to use?

Use the com error handler functionality to trap the error until it no longer appears.

[water]

Use the com error handler functionality to trap the error until it no longer appears.

Thanks for the reply! That's what I was thinking of as well - but I hoped there was a more "elegant" method

[Richard Robertson]

Blame Microsoft. That was a pretty poor design decision to load a library asynchronously.

[water]

OK, I'm going to blame M$

Do you think they will then solve the problem