I created a rule to run a custom VBA script to parse incoming emails
for specific items and add the data to an Excel workbook. I wrote and
tested the code in Outlook 2007 on a WinXP machine (SP3) and
everything worked perfectly. When I deployed the macro to the target
machine (Outlook 2007 on Windows 7), the VBA code is not running at
all. I verified this by removing all of the code and leaving only a
msgbox command which was never displayed. I had the user check the
macro security settings - they were set to allow macros to run; I also
had her double-check the references to make sure the Excel 12 Object
Library was included.

Since the code works on XP but never even gets called on Windows 7, I
can only assume it is something OS-specific. I am pretty experienced
with VBA for Office products and Windows in general, but I have
absolutely no experience with Windows 7 so I'm clueless about what the
problem might be or where to go to resolve it. To make matters worse,
I'm trying to walk the user through the installation process over the
phone and I'm pretty much fumbling around in the dark by not being
able to see what she sees or or look for "old friends with new names"
so to speak.

I do not know if the user is running Windows 7 64-bit or 32-bit. I am
trying to find out just in case that makes a difference.

Any insight, suggestions, kicks in the right direction, or sympathy
flames against MS for making my life miserable with this issue is
greatly appreciated.

Thanks.