It is possible to avoid 'compile Error' when calling another macro and
that macro doesn't exists, by using Application.Run.

So, instead of using

Call TheOtherMacro

....you use:

Application.Run "TheOtherMacro"

That way the original macro will still compile, even if 'TheOtherMacro'
doesn't exists (yet).


Is it possible to do something similar with UserForms???

If I use:

UserForm1.Show

....and the userForm doesn't exists yet, the code will error during
compile time, but I need my UserForm to be created during macro run, so
is it possible to avoind compile error, if a UserForm doesn't exists
yet, just as if a macro doesn't exists at compile time???


Thanks,

CE

It is possible to avoid 'compile Error' when calling another macro
and that macro doesn't exists, by using Application.Run.

So, instead of using

Call TheOtherMacro

...you use:

Application.Run "TheOtherMacro"

That way the original macro will still compile, even if
'TheOtherMacro' doesn't exists (yet).


Is it possible to do something similar with UserForms???

If I use:

UserForm1.Show

...and the userForm doesn't exists yet, the code will error during
compile time, but I need my UserForm to be created during macro run,
so is it possible to avoind compile error, if a UserForm doesn't
exists yet, just as if a macro doesn't exists at compile time???


Thanks,

CE

The purpose of compiling code is to very that it will execute without
error at runtime. That precludes, then, that all refs exist at compile
time! For example, using 'Call TheOtherMacro' will compile so long as
the procedure exists, *even if it's empty*! Same holds true for objects
and external refs!

So.., just add the userform and let it sit there until you're ready to
design it.

--
Garry

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