hey Chip

thanks a lot for the help.
Will have a look at the tool.
Will surely come in handy!

yours

Carlo

"Chip Pearson" wrote:

Carlo,

When you get bizarre code execution errors, such as code execution jumping
into unrelated procedures, it often is due to messiness in VBA's internal
code storage mechanism. When you do a lot of editing of a VBA project, VBA
doesn't always fully and completely delete its own version of the code you
edit. (This is not something you are doing wrong -- it is all internal to
VBA itself.) The preferred solution is to export all your VBA code to text
files, Remove the modules from the project, and then re-import the saved
text files. This causes VBA to purge its internal storage of the code and
start with a clean slate. Rob Bovey has written a fine and free add-in to do
this automatically. Go to
http://www.appspro.com/Utilities/CodeCleaner.htm and download CodeCleaner
4.4. It will add an item to your Tools menu named "Clean Project". Note that
the VBA project must be unlocked. Also, see the note on that web page
regarding protection in Excel 2002 and 2003.

Cleaning the VBA Project can clear up lots of bizarre behavior in your code.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel
www.cpearson.com
(email address is on the web site)




"Carlo" wrote in message
...
Hi everybody

by changing the printarea of a sheet with VBA, my code jumps to the
onchange
code of a Combobox, which has nothing to do with the printarea.

To be more precisely: after initializing the form, the changing of the
printarea
works fine, after using the combobox, the changing of the printarea
triggers
the
onchange event of the combobox. It's always the same combobox!
In the code of the combobox i change the printarea too, but that shouldn't
be the
problem, because it shouldn't get activated at all!

Anyone had some similar issues?

Thanks for any help

Carlo