RE: Too much coding for macro?
- From: Sam Wilson <SamWilson@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 13 Aug 2009 01:28:02 -0700
Just insert three modules, put the coding for B in one in a macro called
main_b, the coding for C in another called main_c and in the third something
like:
sub master()
'logical check to see if A applies
if ... then call main()
'logical check to see if B applies
if ... then call main_b()
'logical check to see if C applies
if ... then call main_c()
end sub
"Eric" wrote:
Does anyone have any suggestions on how to handle too much coding for macro?.
Under the macro coding, the structure is shown below
Sub main()
A set of coding for A class
...
A set of coding for B class
...
A set of coding for C class
...
End Sub
When there is only coding for A class, there is no problem on running macro,
but when I insert the coding for B class, it pops up something like too much
coding for macro. Does anyone have any suggestions on how to split coding
into different module? so I still can run macro by referring to different
module.
Does anyone have any suggestions?
Thanks in advance for any suggestions
Eric
- References:
- Too much coding for macro?
- From: Eric
- Too much coding for macro?
- Prev by Date: Too much coding for macro?
- Next by Date: RE: importing data from excel to sql server 2008 by code at run time
- Previous by thread: Too much coding for macro?
- Next by thread: RE: Too much coding for macro?
- Index(es):
Relevant Pages
|
