Originally Posted by
TMS
I do see the option to use the "new" Outlook interface. Is that what you mean?
Yes, that's exactly the switch I'm thinking of. Switching to a new interface causes, problems with the operation of automation, about which below.
Originally Posted by
6StringJazzer
What "new Outlook" are you taking about?
Please refer to this article, possibly additional googling.
Originally Posted by
ByteMarks
Still, it shouldn't crash Excel should it? You'd expect a "Can't create object" error.
That's the way it should be, but things are mixed with Microsoft.
I ran a short test a moment ago on version 365. In Outlook, I switched the view to "new Outlook." I closed the application, checked in the Task Manager to see if Outlook stayed among the background tasks. It was not there. In Excel, I ran the following code:
The execution of the code stopped for about 20 sec on the line CreateObject("Outlook.Application") and then reported the exception:"-2146959355 (80080005) Server execution failed". The variable oOtlk = Nothing.
I ran the code again. The execution again stopped for a moment at the CreateObject line, and then returned an Outlook message: "We detected a problem when starting a new Outlook. Try again later." Err.Number = 0, Err.Description = "", the oOtlk variable contained a reference to the Outlook application. After completing the macro, I opened Outlook and.... by itself returned to the old view. Subsequent running of the code was already running smoothly, of course.
That's where I ended the test.
Artik
Bookmarks