>>>>UPDATE - I have disabled the addobject code for two of the seven above mentioned. The 7x365 gave around 5970 destroys. It'll now be around 4260 destroys. The original 47 seconds became 14 seconds. And when doing a removeobject() via an explicit loop this became 7 seconds.
>>>>
>>>>My hunch is that there is a certain amount of workspace that is extended if the number of objects becomes too large and that will cause a slower destroy. The lesson: VFP can handle many objects, but if there are very many then destruction will slow down.
>>>>
>>>>Perhaps there's some type of memory that could be increased?!
>>>
>>>Play with SYS(3050).
>>
>>This is what I did yesterday. No effects found.
>>
>>One question though. I get a negative default value. How can I interpret that?
>
>Haven't seen that. I wonder if it means you have so much memory, you're outside the range the function expects.
>
>Tamar

If I'm not mistaken, an negative value indicates a value above 2^31 (~ 2GB) -- signed 32-bit value goes from -2,147,483,648 to 2,147,483,647 (an unsigned would go from 0 to 4,294,967,295)