First off I am not very knowlegeable about Outook or VBA coding so I
apologize in advance for missing the obvious.

I have created some rules in outlook (actually exported/imported from a
functioning account). The rules basically:
-look for an email with an attachment and with a specific word in the
subject line
-move the email to a different folder
-copy the attachment and place it in a shared system folder (done with VBA
code)

The problem I have is the rules will only work until Outlook is closed down
or the server is rebooted. After that the rules partially work (the VBA code
doesn't). The VBA code is still visible in the editor and the rules still
point to the applicable VBA script. However, the code just doesn't run.

To get around the problem, I delete the .otm file and rebuild (via import of
the .bas files) the VBA project, save it, and close the VBA editor. Until I
close down Outlook again the rules all function properly.

Could anyone describe to me where i am going wrong.

Thanks,
John

Does other VBA code run? If not, check your macro security settings. You
might also put a Debug.Print statement in the Application_Startup event
handler to "wake up" the VBA environment.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"John66" wrote in message
...
First off I am not very knowlegeable about Outook or VBA coding so I
apologize in advance for missing the obvious.

I have created some rules in outlook (actually exported/imported from a
functioning account). The rules basically:
-look for an email with an attachment and with a specific word in the
subject line
-move the email to a different folder
-copy the attachment and place it in a shared system folder (done with VBA
code)

The problem I have is the rules will only work until Outlook is closed
down
or the server is rebooted. After that the rules partially work (the VBA
code
doesn't). The VBA code is still visible in the editor and the rules still
point to the applicable VBA script. However, the code just doesn't run.

To get around the problem, I delete the .otm file and rebuild (via import
of
the .bas files) the VBA project, save it, and close the VBA editor. Until
I
close down Outlook again the rules all function properly.

Could anyone describe to me where i am going wrong.

Thanks,
John

Thank you so very much for your help!

The security settings were the problem.

"Sue Mosher [MVP]" wrote:
Does other VBA code run? If not, check your macro security settings. You
might also put a Debug.Print statement in the Application_Startup event
handler to "wake up" the VBA environment.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"John66" wrote in message
...
First off I am not very knowlegeable about Outook or VBA coding so I
apologize in advance for missing the obvious.

I have created some rules in outlook (actually exported/imported from a
functioning account). The rules basically:
-look for an email with an attachment and with a specific word in the
subject line
-move the email to a different folder
-copy the attachment and place it in a shared system folder (done with VBA
code)

The problem I have is the rules will only work until Outlook is closed
down
or the server is rebooted. After that the rules partially work (the VBA
code
doesn't). The VBA code is still visible in the editor and the rules still
point to the applicable VBA script. However, the code just doesn't run.

To get around the problem, I delete the .otm file and rebuild (via import
of
the .bas files) the VBA project, save it, and close the VBA editor. Until
I
close down Outlook again the rules all function properly.

Could anyone describe to me where i am going wrong.

Thanks,
John


.

Which security settings? I have this problem also, but it's not clear which security settings in my version of Outlook (Enterprise 2007 12.0.6514.5000 SP2 MSO 12.0.6536.5002) have anything to do with VBA scripts not running after a restart.