I had the same problem. I do believe it is a Microsoft "BUG". Sometimes my
rules work and sometimes they don't. Often, I had to run manually. All in
all, the rules I set worked just fine when run manually. Even after
performing all the tips and tricks from MVP Outlook professionals, I still
had the same problem !!!! Here is my solution that WORKED for me as my rules
NOW run automatically with my VBA scripts.
a) Click Tools, Macro, Visual Basic Editor.
b) In the project explorer to the left, expand Microsoft Office Outlook
Objects
c) Double Click "ThisOutlookSession"
d) Copy and past the following code
Private Sub Application_Startup()
MsgBox "Welcome, " & Application.GetNamespace("MAPI").CurrentUser
Application.ActiveExplorer.WindowState = olMaximized
End Sub
e) Save the Visual Basic Program.
f) Close.
g) Done.
I know this doesn't make sense, but I think that the VBA macro library is
NOT loading properly at the start of Microsoft Outlook. I think the startup
event forces the loading of the VBA scripts properly. I don't think it
matters what code you place just as long as it is something to properly start
the VBA macros.
Anyway, again, I know that the above doesn't make any sense but it WORKED
for me. All the other LOGICAL solutions by the MVP professionals and other
users simply just did not work, which those other solutions should have
worked. Therefore, this leads me to believe that there is a BUG is the
Outlook product.
Again, it worked for me and I am NOW happy and I have stopped wasting hours
looking for a solution.
If this SOLUTION worked for you, please let me know. If this solution works
for you, please make a post so that Microsoft will know where to look for
this goofy bug in the Outlook product.
I hope this works for you as I spent over 200 hours trying to fix this same
problem.
John R. Hamilton