>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.

Try what, set all these references to null in destroy, instead of making them vanish automatically? If not necessary, I've heard some who say it's cleaner (and relieves you of the danger of dangling references) and, who knows, may make it faster. Report here with the results, please.