not fully on topic - in one large app scenario we skip form destruction if shutdown event is asked for -
we walk all forms to close tables, but then kill process while 0..n forms may still be instatiated. Best optimization is to skip running unneccessary code ;-)

>The formclass I recently developed can have as much as over 1800 objects. What strikes me is that it builds the form in a snap, but it requires almost a minute to 'destroy'.
>There's no special, time consuming, code in any Destroy(). And only some have some code in their QueryUnload() or Release().
>Who knows of any trick to speed up the destruction of the form?
>Perhaps it's the fact that a subset of those objects have properties that refer to other objects? Hmm, I'll gonna try this out.