>>Stefan.
>>
>>dealing with Dynamics for years I think this is nice for readability - but worst for performance. It will call the method over and over and this will slow down the grid to much.
>
>Hi Agnes,
>Interesting point - I never had that impression; made a test that seems to indicate almost no difference, what do you think?

As I said elsewhere in this thread, with today's machines, it almost doesn't matter, unless you're running a huge grid and you have multiple dynamic properties which call form's methods. Calling grid's methods is an unlikely scenario - you can do that in a prg-based grid on a form, but in a vcx it just won't save (actually will, but won't recognize later) a method added to a member object, so it would have to be either a method in your grid class (and how many people will subclass a grid just to have acustom dynamic* method?), or a form's method, where you can add as many as you want without creating any extra entities.

Last time I had one like that, it was a 1000px wide grid with about 30 rows, on the motherboard before this - a 1.7GHz Athlon with 512M, a very fast one for the times, and yep, it did slow down when I introduced a complicated dynamic* call. With a 3GHz motherboard, Fox just won't make it sweat enough... until you have a debugger open. Then just watch it slow down and run up the processor.

Still much better than when I first observed this in 2000, VFP6 on a 200MHz box, if anything triggered a grid refresh while I was in the trace window, I simply took a walk - made coffee, took a leak... and by the time I was back, I could press F8.