Many thanks, you suggestion works.

That is spooky behavior. I will definitely look into that code cleaner.

"Simon Murphy" wrote:

try edit replace option explicit with 'option explicit, compile, then put
back the option explicit
VBA does cache a copy of your vba code in byte code, changing option
explicit forces it to re compile properly
This is not a good sign though - be sure to use Rob Boveys code cleaner
asap - from www.appspro.com
cheers
Simon

"alainr" wrote in message
...
Excel does not seem to be using the version of a macro that is attached to
the worksheet module. Any changes I make to the module (breakpoints, code
change, etc...) at not reflected when I call the macro (either from the
VBA
interface or from Excel worksheet push-button or from Macro menu). I
tried
to open and close Excel, and still... I can't make a change to my macro.

Is it possible that there is a cached version of my old VBA module hidden
somewhere??

What is going on?