Does Size Matter?

[Greg Bloom]

Is there a size limitation on how much code can be placed in a user form? I
am starting to get messages that appear to be out of memory erorrs.

 

[Don Guillett]

Sorry, I couldn't resist.
On the subject line, "Some girls think so"
<G>

 

[Tom Ogilvy]

Generally, modules should be held to under 64K - at least that is the advice
I have seen given here.

 

[Phobos]

I suppose someone had to...

<g>

P

Sorry, I couldn't resist.
On the subject line, "Some girls think so"
<G>
form?

 

[Chrissy]

Don Guillett wrote

Sorry, I couldn't resist.
On the subject line, "Some girls think so"

Most don't.


I think it matters - I am using a 15" monitor now cos my 21" one
died and I am a poor student. I was using a 21" for 6 years and
SIZE DOES MATTER.

Chrissy.

 

[Chrissy]

How do I see how big a module is?

Chrissy.


Tom Ogilvy wrote

 

[David McRitchie]

The only way I know to find the module size is to export it and then check the
size. I think that is the actual method used in

Excel Code Documenter
Developed by Rob Bovey, MCSE. The Excel 97 Code Documentor automatically documents
the "vital ... number of procedures, DLL declarations, module size and lines of ...
http://www.payneconsulting.com/payneconsultingold/ office/Excel/excelcodedocumenter.htm

 

[David McRitchie]

Sorry that was an old link for Rob Bovey's use this one instead:

Excel VBA Code Documentor
http://www.appspro.com/utilities/Documentor.asp

The Excel 97 Code Documentor automatically documents the "vital statistics"
of your VBA project. These statistics include:
A complete procedure listing for all modules in an outlined worksheet
A summary of the number and type of VBComponents used in the project
The number of procedures in the project, both total and per VBComponent
The number of DLL declarations in the project, both total and per VBComponent
Total lines of code in the project and per VBComponent
Module file size for each code module

--

For keeping track of your Functions and Subroutines, I have
Sub ListFunctionsAndSubs()
'Documented in http://www.mvps.org/dmcritchie/excel/buildtoc.htm
'Coding: http://www.mvps.org/dmcritchie/excel/code/listfsubs.txt
will overwrite content of the worksheet it is run in, it will identify duplicate
subroutines and functions and which book they are in, along the the number
of code lines in each sub or function. The Workbooks that are
included in the documentation are the workbooks that are open when run.
---
HTH,
David McRitchie, Microsoft MVP - Excel [site changed Nov. 2001]
My Excel Pages: http://www.mvps.org/dmcritchie/excel/excel.htm
Search Page: http://www.mvps.org/dmcritchie/excel/search.htm

The only way I know to find the module size is to export it and then check the
size. I think that is the actual method used in

Excel Code Documenter
Developed by Rob Bovey, MCSE. The Excel 97 Code Documentor automatically documents
the "vital ... number of procedures, DLL declarations, module size and lines of ...
http://www.payneconsulting.com/payneconsultingold/ office/Excel/excelcodedocumenter.htm
---
HTH,
David McRitchie, Microsoft MVP - Excel [site changed Nov. 2001]
My Excel Pages: http://www.mvps.org/dmcritchie/excel/excel.htm
Search Page: http://www.mvps.org/dmcritchie/excel/search.htm

How do I see how big a module is?

 

[Chrissy]

I like that Documentor BUT ...... I want to document an XLA and, unless
I missed something, I don't think I can.

Another thing - does it would on Excel XP as I usually run that but do not
have it running now to test.

Chrissy.

David McRitchie wrote

 

[Chip Pearson]

Chrissy,

Change the IsAddIn property of the XLA workbook to False so that it becomes
visible in Excel, and then run the code documentor. Then, set IsAddIn back
to True. Yes, it works fine in Excel XP.