MacroEcon1337
Board Regular
- Joined
- Mar 16, 2017
- Messages
- 65
Okay it is what you think 
1. I made a GIGANTIC code which traverses the entire workbook. And right when I was almost done, I got "procedure too large." This appears to be because the compized size of teh sub is > 64 kb.
2. I do not want to break into two subs, because the setup is so complex. And despite the size, everything is so logical and ordered.
3. What's interesting is I am RIGHT ON THE CUSP of too large - i know exactly which if statement put me over.
4. For others with similar problem, I found GREAT tips (on how to shrink compile size) here:
https://stackoverflow.com/questions/11450232/getting-error-procedure-too-large-in-vba-macros-excel
My only question here is: does variable type (ie dimming as VARIANT instead of INTEGER) affect compile size - or only run speed?
MC
1. I made a GIGANTIC code which traverses the entire workbook. And right when I was almost done, I got "procedure too large." This appears to be because the compized size of teh sub is > 64 kb.
2. I do not want to break into two subs, because the setup is so complex. And despite the size, everything is so logical and ordered.
3. What's interesting is I am RIGHT ON THE CUSP of too large - i know exactly which if statement put me over.
4. For others with similar problem, I found GREAT tips (on how to shrink compile size) here:
https://stackoverflow.com/questions/11450232/getting-error-procedure-too-large-in-vba-macros-excel
My only question here is: does variable type (ie dimming as VARIANT instead of INTEGER) affect compile size - or only run speed?
MC
