>>>And the cost of passing a parameter and parsing its properties 30000 times vs properties being accessed in the WITH context? Consider that this has to happen in real time, i.e. between a click and the time the user expects to see some results.
>>
>>Passed by reference, is it any worse than the WITH? Certainly more obvious what object is being acted upon? :)
>
>Yupp. Function/Method calling are slow operations in vfp, and parameter passing makes it progressively worse.
>This is not a statically type language. For such tight loop situations I also move away from parameter passing,
>but instead of with I prefer privates so oddly named, that conflict is nearly impossible.
>For a use case as Dragan describes, the with has a certain charme - as long as all coders know the dangers.

I'm alone in that neck of the app's woods, and I comment generously.