shonadle
asked on
Issues with Outlook VB script
I posted a question last month which was answered in a timely manner.
It worked so well, I actually set the script to run on two computers running Outlook: Outlook 2010 and 2013.
As of today, the script has quit working. No updates were made to either machine. Only Outlook was restarted. Now with it no longer working, I'm scratching my head trying to figure out why it would stop, especially on two different computers.
I admit when I set the script up initially, I never stopped Outlook again until today.
What I want is when Outlook forwards an email, it changes "FW" to "FWD". I have checked my macro security where the default was selected but went so far as to set it to allow all macros to run. Since that didn't fix it, I set it back to Notifications for digitally signed macros, all other macros disabled.
It worked so well, I actually set the script to run on two computers running Outlook: Outlook 2010 and 2013.
As of today, the script has quit working. No updates were made to either machine. Only Outlook was restarted. Now with it no longer working, I'm scratching my head trying to figure out why it would stop, especially on two different computers.
I admit when I set the script up initially, I never stopped Outlook again until today.
What I want is when Outlook forwards an email, it changes "FW" to "FWD". I have checked my macro security where the default was selected but went so far as to set it to allow all macros to run. Since that didn't fix it, I set it back to Notifications for digitally signed macros, all other macros disabled.
David Lee
Can you post the code or a link to your previous question so we can see the code?
ASKER
I did. It's in my first post but here is another link to the other question:
https://www.experts-exchange.com/questions/28323742/Convert-Outlook-forward-from-fw-to-fwd.html?anchorAnswerId=39752638#a39752638
https://www.experts-exchange.com/questions/28323742/Convert-Outlook-forward-from-fw-to-fwd.html?anchorAnswerId=39752638#a39752638
Oops. Sorry, I missed the link.
The code is in place in the ThisOutlookSession module, macros are enabled, and the code isn't working. Is that correct?
ASKER
Yes. It was working GREAT! Then I restarted Outlook (first on the 2013 version). When I did that, it stopped working. Tried repasting code over and over, to no avail.
Played around with the macro settings, to see if setting them really low would pop it back in. No. I then looked at the outlook 2010 version because it also had been working to see if there was a difference. That's when I noticed it had quit working. It was restarted during this experiment too.
I did not do any Windows updates in this time. Both are running Windows 7 with one on Office 2013 and the other on Office 2010.
Played around with the macro settings, to see if setting them really low would pop it back in. No. I then looked at the outlook 2010 version because it also had been working to see if there was a difference. That's when I noticed it had quit working. It was restarted during this experiment too.
I did not do any Windows updates in this time. Both are running Windows 7 with one on Office 2013 and the other on Office 2010.
What is Outlook's macro security set to?
ASKER
Originally "Notifications for digitally signed macros, all other macros disabled. Since this happened I set it down to Enable all macros. I also checked the Apply macro security settings to installed add ins on and off.
Ok. Add this code to what you already have in ThisOutlookSession. Once you've added the code, close and restart Outlook. Tell me what happens after restarting.
Private Sub Application_Startup()
MsgBox "Macros are enabled."
End SubASKER
No, sorry. Tried it in both the 2013 and 2010 versions, still shows the sent email as "FW" instead of "FWD". (I did restart Outlook by the way).
That wasn't designed to fix the problem, It was to test and see what's going on. What happened when you restarted Outlook? Did you get a dialog-box? If you didn't, then macros are not enabled despite the fact that they are set to be enabled.
ASKER
oh sorry. I didn't get a dialogue box.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, well I did not get a dialog box. However, the script is working again. It changed Fw to FWD.
I'm going to go back in and take out that second script and see if it still works.
I'm going to go back in and take out that second script and see if it still works.
ASKER
Yes it still works.
I find it odd that this issue happened on two different computers with two different versions of Outlook. It's almost like that VB script had gotten corrupted and needed to be removed. (which luckily you told me how to do).
I find it odd that this issue happened on two different computers with two different versions of Outlook. It's almost like that VB script had gotten corrupted and needed to be removed. (which luckily you told me how to do).