Have a function in ThisOutlookSession which is called by a rule when
email arrives from specific persons. Worked perfectly for awhile, then
stopped working. Reinstalled Outlook, put the function back in, and it
started working again. Now it has stopped again. I think this is the
main clue: I have "Warnings for all macros" checked in Trust Center.
While it was working, I got the warning every time. Now I never get
it. It behaves as if I had "No warnings and disable all macros"
checked instead. Is this some kind of bug in Trust Center? Anyone
know how to check the registry to see what the actual setting is? By
the way, this time before it stopped working I saw a dialog to the
effect that the function had somehow failed, after a triggering email
had arrived. After that, it no longer worked, and no messages are
seen. Don't know if that message was cause or effect.

Probably Outlook has disabled your code after the failure. You can check
that via Help/Disabled Items and see if VBA is listed there.

So, to get it reliably running you need to fix your code.

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:
http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Tue, 07 Aug 2007 06:41:08 -0700 schrieb :

Have a function in ThisOutlookSession which is called by a rule when
email arrives from specific persons. Worked perfectly for awhile, then
stopped working. Reinstalled Outlook, put the function back in, and it
started working again. Now it has stopped again. I think this is the
main clue: I have "Warnings for all macros" checked in Trust Center.
While it was working, I got the warning every time. Now I never get
it. It behaves as if I had "No warnings and disable all macros"
checked instead. Is this some kind of bug in Trust Center? Anyone
know how to check the registry to see what the actual setting is? By
the way, this time before it stopped working I saw a dialog to the
effect that the function had somehow failed, after a triggering email
had arrived. After that, it no longer worked, and no messages are
seen. Don't know if that message was cause or effect.

In Outlook 2007, that would be Tools | Trust Center | Add-ins | Disabled Items.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"Michael Bauer [MVP - Outlook]" wrote in message .. .


Probably Outlook has disabled your code after the failure. You can check
that via Help/Disabled Items and see if VBA is listed there.

So, to get it reliably running you need to fix your code.

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:
http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Tue, 07 Aug 2007 06:41:08 -0700 schrieb :

Have a function in ThisOutlookSession which is called by a rule when
email arrives from specific persons. Worked perfectly for awhile, then
stopped working. Reinstalled Outlook, put the function back in, and it
started working again. Now it has stopped again. I think this is the
main clue: I have "Warnings for all macros" checked in Trust Center.
While it was working, I got the warning every time. Now I never get
it. It behaves as if I had "No warnings and disable all macros"
checked instead. Is this some kind of bug in Trust Center? Anyone
know how to check the registry to see what the actual setting is? By
the way, this time before it stopped working I saw a dialog to the
effect that the function had somehow failed, after a triggering email
had arrived. After that, it no longer worked, and no messages are
seen. Don't know if that message was cause or effect.

You're right. But at least for the German Outlook it's also available under
the Help menu.

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:
http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Wed, 8 Aug 2007 08:11:13 -0400 schrieb Sue Mosher [MVP-Outlook]:

In Outlook 2007, that would be Tools | Trust Center | Add-ins | Disabled
Items.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"Michael Bauer [MVP - Outlook]" wrote in message
.. .


Probably Outlook has disabled your code after the failure. You can check
that via Help/Disabled Items and see if VBA is listed there.

So, to get it reliably running you need to fix your code.

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:

http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Tue, 07 Aug 2007 06:41:08 -0700 schrieb :

Have a function in ThisOutlookSession which is called by a rule when
email arrives from specific persons. Worked perfectly for awhile, then
stopped working. Reinstalled Outlook, put the function back in, and it
started working again. Now it has stopped again. I think this is the
main clue: I have "Warnings for all macros" checked in Trust Center.
While it was working, I got the warning every time. Now I never get
it. It behaves as if I had "No warnings and disable all macros"
checked instead. Is this some kind of bug in Trust Center? Anyone
know how to check the registry to see what the actual setting is? By
the way, this time before it stopped working I saw a dialog to the
effect that the function had somehow failed, after a triggering email
had arrived. After that, it no longer worked, and no messages are
seen. Don't know if that message was cause or effect.

Great! That's easier for people to find. THanks for pointing thatout.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"Michael Bauer [MVP - Outlook]" wrote in message ...


You're right. But at least for the German Outlook it's also available under
the Help menu.

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:
http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Wed, 8 Aug 2007 08:11:13 -0400 schrieb Sue Mosher [MVP-Outlook]:

In Outlook 2007, that would be Tools | Trust Center | Add-ins | Disabled
Items.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"Michael Bauer [MVP - Outlook]" wrote in message
.. .


Probably Outlook has disabled your code after the failure. You can check
that via Help/Disabled Items and see if VBA is listed there.

So, to get it reliably running you need to fix your code.

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:

http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Tue, 07 Aug 2007 06:41:08 -0700 schrieb :

Have a function in ThisOutlookSession which is called by a rule when
email arrives from specific persons. Worked perfectly for awhile, then
stopped working. Reinstalled Outlook, put the function back in, and it
started working again. Now it has stopped again. I think this is the
main clue: I have "Warnings for all macros" checked in Trust Center.
While it was working, I got the warning every time. Now I never get
it. It behaves as if I had "No warnings and disable all macros"
checked instead. Is this some kind of bug in Trust Center? Anyone
know how to check the registry to see what the actual setting is? By
the way, this time before it stopped working I saw a dialog to the
effect that the function had somehow failed, after a triggering email
had arrived. After that, it no longer worked, and no messages are
seen. Don't know if that message was cause or effect.

On Aug 8, 1:44 am, "Michael Bauer [MVP - Outlook]"
wrote:
Probably Outlook has disabled your code after the failure. You can check
that via Help/Disabled Items and see if VBA is listed there.

So, to get it reliably running you need to fix your code.

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:
http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Tue, 07 Aug 2007 06:41:08 -0700 schrieb :



Have a function in ThisOutlookSession which is called by a rule when
email arrives from specific persons. Worked perfectly for awhile, then
stopped working. Reinstalled Outlook, put the function back in, and it
started working again. Now it has stopped again. I think this is the
main clue: I have "Warnings for all macros" checked in Trust Center.
While it was working, I got the warning every time. Now I never get
it. It behaves as if I had "No warnings and disable all macros"
checked instead. Is this some kind of bug in Trust Center? Anyone
know how to check the registry to see what the actual setting is? By
the way, this time before it stopped working I saw a dialog to the
effect that the function had somehow failed, after a triggering email
had arrived. After that, it no longer worked, and no messages are
seen. Don't know if that message was cause or effect.- Hide quoted text -

- Show quoted text -

Vielen dank, Michael, aber leiter ... that's apparently not the
problem. No items are disabled. Have there been no reports of Outlook
behaving as if a person had checked "...disable all macros?" Thanks
for your help.

I don't know that reports, maybe it's the Run-a-Script-Rule that isn't as
stable as it should be.

However, you might check what happens if you set the macro security settings
to Very Low. If that doesn't help you could show your code here, maybe we
find an error.

(As setting commas in German is very different from the English rules, you
did it absolutely correct. Really good

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:
http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Wed, 08 Aug 2007 13:29:50 -0700 schrieb :

On Aug 8, 1:44 am, "Michael Bauer [MVP - Outlook]"
wrote:
Probably Outlook has disabled your code after the failure. You can check
that via Help/Disabled Items and see if VBA is listed there.

So, to get it reliably running you need to fix your code.

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:

http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Tue, 07 Aug 2007 06:41:08 -0700 schrieb :



Have a function in ThisOutlookSession which is called by a rule when
email arrives from specific persons. Worked perfectly for awhile, then
stopped working. Reinstalled Outlook, put the function back in, and it
started working again. Now it has stopped again. I think this is the
main clue: I have "Warnings for all macros" checked in Trust Center.
While it was working, I got the warning every time. Now I never get
it. It behaves as if I had "No warnings and disable all macros"
checked instead. Is this some kind of bug in Trust Center? Anyone
know how to check the registry to see what the actual setting is? By
the way, this time before it stopped working I saw a dialog to the
effect that the function had somehow failed, after a triggering email
had arrived. After that, it no longer worked, and no messages are
seen. Don't know if that message was cause or effect.- Hide quoted text
-

- Show quoted text -

Vielen dank, Michael, aber leiter ... that's apparently not the
problem. No items are disabled. Have there been no reports of Outlook
behaving as if a person had checked "...disable all macros?" Thanks
for your help.

These symptoms can also come up if another program starts Outlook with no UI. Shutting down Outlook and making sure Outlook.exe is not running usually makes it possible to restart Outlook and get VBA working again.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"Michael Bauer [MVP - Outlook]" wrote in message .. .


I don't know that reports, maybe it's the Run-a-Script-Rule that isn't as
stable as it should be.

However, you might check what happens if you set the macro security settings
to Very Low. If that doesn't help you could show your code here, maybe we
find an error.

(As setting commas in German is very different from the English rules, you
did it absolutely correct. Really good

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:
http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Wed, 08 Aug 2007 13:29:50 -0700 schrieb :

On Aug 8, 1:44 am, "Michael Bauer [MVP - Outlook]"
wrote:
Probably Outlook has disabled your code after the failure. You can check
that via Help/Disabled Items and see if VBA is listed there.

So, to get it reliably running you need to fix your code.

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:

http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Tue, 07 Aug 2007 06:41:08 -0700 schrieb :



Have a function in ThisOutlookSession which is called by a rule when
email arrives from specific persons. Worked perfectly for awhile, then
stopped working. Reinstalled Outlook, put the function back in, and it
started working again. Now it has stopped again. I think this is the
main clue: I have "Warnings for all macros" checked in Trust Center.
While it was working, I got the warning every time. Now I never get
it. It behaves as if I had "No warnings and disable all macros"
checked instead. Is this some kind of bug in Trust Center? Anyone
know how to check the registry to see what the actual setting is? By
the way, this time before it stopped working I saw a dialog to the
effect that the function had somehow failed, after a triggering email
had arrived. After that, it no longer worked, and no messages are
seen. Don't know if that message was cause or effect.- Hide quoted text
-

- Show quoted text -

Vielen dank, Michael, aber leiter ... that's apparently not the
problem. No items are disabled. Have there been no reports of Outlook
behaving as if a person had checked "...disable all macros?" Thanks
for your help.

Thanks Sue, I didn't know that.

--
Viele Gruesse / Best regards
Michael Bauer - MVP Outlook
Organize eMails:
http://www.vboffice.net/product.html?id=2006063&cmd=detail&lang=en&pub=6

Am Thu, 9 Aug 2007 07:03:52 -0400 schrieb Sue Mosher [MVP-Outlook]:

These symptoms can also come up if another program starts Outlook with no
UI. Shutting down Outlook and making sure Outlook.exe is not running usually
makes it possible to restart Outlook and get VBA working again.