VBA was working now stopped

  • Thread starter Thread starter Neil Jarman
  • Start date Start date
N

Neil Jarman

Hello,

I have a VBA app written in Outlook 2002. It worked fine when machine was
stand-alone.

Last week joined a domain and Exchange setup.

Copied the code to new user (on same machine) and it worked for 3 days.

Since then the code does not run, and this is evidenced by the
Application_Startup code not being called, and myOlApp_NewMail not firing.

Have seen the KB article but have done as suggested and this does not help
(it says do Alt-f11 to re-connect)

Have also tried to run the code from Outlook 2003 but this didn't wotk
either,.

Am I missing something totally obvious?

Please help as this is causing my great troubles.

Many Thanks

NEIL
 
Does even the simplest VBA macro run? Did you check the macro security
setting for the new user?
 
check the security, if it is High, unsigned macros will not run. Create
Digital signature and attach it to the code.

Hope this helps
 
It's not a macro, it's code - is this different?

No longer on site so can't easily say.

But, to answer your question, Application_Startup was simple - "Msgbox
("Outlook is monitoring ...")" so that's a one liner and it didn't fire.

re security:

I have edited security to medium in the first place when the code did run.

Tried lowest setting today but still didn't run.
 
What I was suggesting was that you write a small macro, if you don't have
one already -- i.e. an argumentless Sub -- and try to run it to see if VBA
is working at all.

In case you haven't already, you must restart Outlook after changing the
security level.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
OK.

No - it is not working.

Neil


Sue Mosher said:
What I was suggesting was that you write a small macro, if you don't have
one already -- i.e. an argumentless Sub -- and try to run it to see if VBA
is working at all.

In case you haven't already, you must restart Outlook after changing the
security level.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
Click to expand...
 
Then, make sure that Outlook macro security is set to Low or Medium, shut
down Outlook, and shut down any programs that might be accessing Outlook --
ActiveSync, a fax program, etc. Use Task Manager (Ctrl+Alt+Del) to make sure
Outlook.exe has shut down. After it does, then try restarting Outlook and
running your test macro.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Back
Top