>>>>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 ?
>
>Forget Mike, he openly confesses problems with his imagination :).
>
>Actually, when the requirements are such, a good OOP design is perhaps the only way to have that many objects efficiently organized.

Actually 10K+ objects in vfp would have me looking for alternate architecture - less in a modal form - but here loading and throwing away chunks of 500 objects may be better usage. 10K+ in vfp needs one or few table(s) - even if half of that is only GUI eye candy. That many objects really needed - esp. if needed in [vfp-GUI] object hierarchy and not in properties - I would turn to Java or C# or C++ by instinct ;-)
>
>An afterthought - if form destruction is so slow (but by now we see Peter has reduced the problem to manageable sizes), perhaps hidden destruction would work. Hide the form, stop its code, then fire a timer and slowly release the objects at some lower level, one container at a time.

Yupp, one nice way