botter_bao
Member
- Outlook version
- Email Account
- Exchange Server
The run a script function stopped unexpectedly in Outlook2007
Hi pals,
I encountered a problem that I found the function of "run a script" is disabled suddenly in my outlook2007, here is the details:
At the beginning, the "run a script" func works fine, and I'm very happy. But about half day later, I found it refused to work! I think I did nothing except adjusted the priority of the rule (by using the up and down arrows). So I changed back its position to the top, but not recovered. I also reboot my computer, and also failed.
Then I started a new rule which is a very simple stub:
Sub test(Item As Outlook.MailItem)
MsgBox "haha"
End Sub
The result is disappointing -- it doesn't work either. I found a similar question before, the link is Problem Getting Outlook 2007 Running VBA Script. As bob-the-destroyer said, it might be a problem of the outlook it self... I just wonder if any more actions could cause this failure? Do I have any more method to troubleshoot this problem? Thanks very much!
P.S. I've changed the Security level to "Warnings for all macros".
Hi pals,
I encountered a problem that I found the function of "run a script" is disabled suddenly in my outlook2007, here is the details:
At the beginning, the "run a script" func works fine, and I'm very happy. But about half day later, I found it refused to work! I think I did nothing except adjusted the priority of the rule (by using the up and down arrows). So I changed back its position to the top, but not recovered. I also reboot my computer, and also failed.
Then I started a new rule which is a very simple stub:
Sub test(Item As Outlook.MailItem)
MsgBox "haha"
End Sub
The result is disappointing -- it doesn't work either. I found a similar question before, the link is Problem Getting Outlook 2007 Running VBA Script. As bob-the-destroyer said, it might be a problem of the outlook it self... I just wonder if any more actions could cause this failure? Do I have any more method to troubleshoot this problem? Thanks very much!
P.S. I've changed the Security level to "Warnings for all macros".