>>I suspect that the removing an object has to rearrange collection properties like controls() and objects() and the larger the number of objects, the more time it takes. This would explain the exponential increase of time needed when large numbers of objects exist.
>
>If this is the case, would manually storing a reference to the objects in instantiation order, and then removing them in that order save some time?

I've tried that. Tought there is a difference in performance depending on the order in which your destroy them, it did not make a lot of difference. I think the VFP team never took these kind of scenarios in mind and never optimized for it.

Walter,