![]() |
Too much coding for macro?
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 |
Too much coding for macro?
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 |
Too much coding for macro?
Alternatively, is it possible that you could use some of the same coding for
B class and C class that you use for A class? You may want to post your code to see if you can get any assistance in streamlining it. If you've recorded most of it, you can probably do a lot of streamlining. "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 |
All times are GMT +1. The time now is 07:27 PM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com