Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I have what's turned into a fairly massive spreadsheet project (file size
approaching (7 MG), getting a bit overloaded with heavily programmed forms and intricate functionalities. Recently have been running into messages "not enough system resources to display" when I'm trying to debug. I have been routinely exporting the forms and modules and reimporting them after making any substantial changes, so the vba compiler can clean itself up. So, to finally get to my questions! Is it excessive of me to have 20 different variables declared as Public? And is it more or less efficient to declare them as Public than within each procedure as they're needed? Any other suggestions on smartly conserving system resources? Does it help to reduce the length of individual procedures? i.e. break them into smaller tasks? Does it help to spread them out accross more modules? Any advice you have will be most appreciated! |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Use of Public for data declaration in Excel 2000 | Excel Programming | |||
More efficient memory deallocation | Excel Programming | |||
Declaration of public variable - Question | Excel Programming | |||
Public declaration | Excel Programming | |||
public declaration | Excel Programming |