CG> I gather MicroSoft is hiring programmers that don't have the skills to
 CG> organize their code these days.  So they end up with dozens of
 CG> subroutines that perform the same kind of things, which if organized,
 CG> one subroutine would handle.  The amount of compiled code sure
 CG> indicates some sloppy design work.
I think the trap they are falling into is the same one that is luring me
into sloppiness - almost limitless memory.  I find that to get a working
version going I would rather change a bit of code slightly and make it a
new Sub/Function than to figure a clever way of using existing code to do
the same thing.  Bloats the code terribly for now.
Goal of course is to go back and make it look better/smaller later.  We all
know how that works.
--- PPoint 2.00
---------------