>>>>>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.
>>>>
>>>>Why you destroy all objects of form? Why don't you just release form?
>>>
>>>Releasing a form destroys all the objects on that form. The issue here is that doing so takes too long.
>>
>>Indeed. IMO, the lesson here is: VFP does destroy quick enough, but if the number of objects is VERY LARGE, then it is an issue that needs attention.
>>
>>When is it very large? We found that 2000 is no problem. However, 5000 or more is troublesome. Somewhat smarter coding should focus on reducing the number of objects.
>
>There you go. It's hard to imagine a proper OO design including a class with 2000 objects.

Is it, Mike ?