application.startup event not firing with exchange login

[sharonpta]

it seems that the application.startup event is not firing, because it seems
to be trumped by my hosted exchange logon dialog box. Whenever I launch
Outlook while working offline, the event fires fine, but when lauched online,
it doesn't fire. Is there any way around this, or is there an event that
fires after successfully logging on to exchange server, possibly after the
status changes to "All folders up to date"?

 

[Ken Slovak - [MVP - Outlook]]

There's an Application.MAPILogonComplete() event, but I doubt that would
fire if your application startup event isn't firing since your addin code
wouldn't be running in that case.

 

[sharonpta]

Yeah. I tried that, and it doesn't fire as well. Do you know why this is
happening, or is there a way to auto login to the exchange server. Another
solution, i was thinking about, is to shell Outlook from another office
product using vba and after 30 seconds or so, run the macro I was wanting to
run at startup. Do you know how to call a macro from another office product
such as word?

 

[Ken Slovak - [MVP - Outlook]]

I don't know why it's happening and I don't use hosted Exchange, so I can't
really recommend a workaround.

Is it possible to set up your connection to the hosted Exchange server to
log you in automatically using your Windows identity, using Windows
Authentication which is what Exchange normally uses?

 

[sharonpta]

This might be a repeat message, the session timed out.

Do you know how to call an external macro from vb6? Microsoft states in a
post how to generate a macro then call it:

Dim xlapp As Object 'Excel.Application
Set xlapp = CreateObject("Excel.Application")
xlapp.Run "MyMacro"
http://support.microsoft.com/kb/194611

But the .run method doesn't exist in the Microsoft Outlook 11 object library
of the object, I made a reference for.

Sharon Taylor

 

[Ken Slovak - [MVP - Outlook]]

The only way for Outlook (unsupported by MS) would be to place the macro as
a Public Sub in the ThisOutlookSession class module. Then you can call it as
Outlook.Application.MySub where "MySub" is the name of your macro.