Reset only occurs if changes are made to executing code

That is not what I see.
I have the code that alters the VBE in a normal module. Code in the userform
(modeless userform)
calls the VBE altering code. The code that is altered is in another normal
module. This other module
has no other code at all and is not called. Still, the reset happens.
It looks the only way you can do this is to put the code to be altered in
another workbook.
That works kind of OK. Module level variables and global variables are still
still there after the code is
altered and while running the altered code. But when the execution of the
altered code is finished
then those variables are reset. The other workbook helps out here, because
it is not running that userform.
I suppose one possible solution would be to run the userform from another
workbook or from an ActiveX dll
but that would be way too much work for too little gain.

RBS


"GS" wrote in message ...
As an after thought, you could put the code in a standard module and call
it from your userform at runtime. Reset only occurs if changes are made to
executing code. A procedure in a standard module won't be executing until
you call it *after* the rewrite.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion