Hi!

Take a look to the MSDN. There is an article somewhere about the optimizing the speed of application. Certain VFP settings have a significant influence on the VFP program running speed. I did read the article, made these settings as default for development mode and forget. I can find it again and post the exact list of commands.

As about the form, it is a simple VFP form just created, 2 comboboxes with the 'Value' row source typoe and some values list in row source, and a shape with a click code. Than put a button, added a code posted here and ran. Memory increased just from the first SetAll call, but than no increases over the entire loop. Increase was ~512 bytes and reduces by ~64 bytes after sys(1104) command use. So, is that 512 additional bytes a problem?

VFP 6.0 SP 3.



>>Hi!
>>
>>Just ran you sample as is for a form with 2 comboboxes and 1 shape objects on form. Nothing happens - memory do not change by SetAll. I have _VFP.AutoYield=.F., SET STATUS BAR OFF and whatever else required to make VFP program run as quick as possible.
>
>Hi Vlad,
>the question now is: What is "wathever else"
>_VFP.AutoYield=.F., SET STATUS BAR OFF did'nt change behaviour.
>
>My form is simple from baseclass with 5 textboxes out of my base vcx,
>and one comandbutton also out of my base
>
>All what is altered on TextBox
>Error event
>
>FontSize = 8
>SelectOnEntry = .t.
>added Properties
>
>
>All what is altered on CommandButton
>Error event
>
>SelectOnEntry = .t.
>added Properties
>
>If I use base classes out of foxpro the behaviour changes again; used memory will count up within the loop. Maybe thats what Nadya mean.
>
>Lutz