>>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?
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
