Once you start editing and saving a template, it bloats; it grows to a size that reflects both the number of times you've saved it and the scope of the changes you've edited.

I make much use of a neat little utility called CodeCleaner. The self-extracting wd97clnr.exe can be found at <A target="_blank" HREF=http://www.payneconsulting.com/Office/Word/word97codecleaner.htm>http://www.payneconsulting.com/Office/Word...codecleaner.htm</A>, and there's now a Word2000 version.

I've been using this utility for over a year (and have inspected the source code too!). There's only one flaw I'm aware of, and that is that source modules appear to collect an extra blank line when re-imported. It's not a major problem.

Why use this utility? Well, it reduces a template from 100K to 50K just like that - faster loading, faster saving, and LESS WORD DEBRIS IN THE FILE. that's gotta be good.


When you start dragging modules with 150 functions into templates because you need some of them, but you're not sure which, ask me about Procedure Stripper. It's not for the faint-hearted. It cross-references every procedure (function or sub) in a template and identifies those which aren't referenced in non-commented code. You get a shopping basket to select procedures to delete. After you've deleted those, ProcStripper re-ezamines the code to detect newly-unreferenced procedures. It does other stuff, too, like sorting procedures in alphabetic sequence in each module, dumping lists of code to the clipboard etc.