XL2003 Macro Visibility

[Mike_B]

Hi Guys

Apologies if this one is an old chestnut but I have searched all over
the net all morning and in here and can't find it.

I have an application which runs fine in XL97/2000. It customises the
whole excel environment removing toobars etc etc and leaving its own
behind (each button being attached to a macro).

Now the odd thing is whenever I click on one of my toolbar buttons I
get (in XL2003 but not in the others..) something like "macro
'filename!macroname' cannot be found".

OK web searches throw up the obvious security thing - right the
security thing is on low - so no answer there.

Investigating further the only macros that can be run from Alt+f8 are a
few indeed (all of them 'subs' not 'public subs' (?!), and uncertain
about option private module effects).

Anyway having read and read and read tearing my hair out here on
something which I hope is trivial for those in the know!

many thanks

Mike

 

[Dave Peterson]

is the filename in 'filename!macroname', open?

Is it in the same location --same drive, same path, same everything for that pc
with xl2003?

 

[Mike_B]

Dave

Thanks for this thought.

Its a different machine and different file path.

However it is a stand-alone Excel file including its own forms
modules, vba code etc etc. This 'file' has been run on many machine
in all sorts of file paths.

The missing macros XL03-VBA is not seeing is in the same file?!?! Th
other odd thing is that it can see a very small number of its 'own
macros but only a small percentage (its not like it can see none o
them).

Still tearing my hair out over this one - the only thing I can think o
is the drastic step of removing all modules, all forms etc etc saving a
a new file and reimporting everything (no small task) - in case it i
one of these 'weird corruption' things.

Before I go down that drastic path though I was just seeking to fin
out whether anyone has tripped over the same problem - ie that an exce
file cant see its own modules's subs!?!?

rgds

Mik

 

[Dave Peterson]

Do you use nice unique names for your macros. Excel can get confused if there
are addins that use the same macro name.