Macro that worked in Excel 2000, gets #NAME? error in 2007 -- suspect Trust Center

[LurfysMa]

We recently upgraded to Office 2007. I have a number of macros in
Excel. I just opened a spreadsheet I use periodically and I get a
#NAME? error in every cell with a macro reference.

I checked the all of the variable and cell names and even called the
function using only constants. The little information icon allows me
to trace execution. It's the function name it is complaining about.

The function is named "MyExp" (for my exponential function). As I
said, this works perfectly in Excel 2000. If I open the exact same
Excel document in 2007, I get these errors.

Do I need to somehow point Excel at my VBA code? If I click Alt+F, I
see the code.

These are my own personal macros. How do I enable them without opening
the doors to potential malware?

Thanks

--

 

[LurfysMa]

We recently upgraded to Office 2007. I have a number of macros in
Excel. I just opened a spreadsheet I use periodically and I get a
#NAME? error in every cell with a macro reference.

I checked the all of the variable and cell names and even called the
function using only constants. The little information icon allows me
to trace execution. It's the function name it is complaining about.

The function is named "MyExp" (for my exponential function). As I
said, this works perfectly in Excel 2000. If I open the exact same
Excel document in 2007, I get these errors.

Do I need to somehow point Excel at my VBA code? If I click Alt+F, I
see the code.

These are my own personal macros. How do I enable them without opening
the doors to potential malware?

PS: A couple of additional points, that I should have included in the
original post:

1. I have checked the "Trust access to the VBA project object model"
in the Trust Center settings.

2. When I "show calculation steps", the function name (MyExp) appears
as "I22MyExp". Is this an error message?

3. As far as I can tell, I have exactly the same Trust Center settings
in Word 2007 and all of my macros from Word 2000 work just fine there.
I do *NOT* have the "Trust access to the VBA project object model"
option checked there.


--