>>>>In my drag-and-drop grid, I am also having a problem with speed. I have cleaned out all of the "extraneous" stuff I can find from any relevant methods, and yet my grid is very slow to move from cell to cell.
>>>>
>>>>What areas typically cause a grid to slow down dramatically?
>>>>
>>>>Paul
>>>
>>>The things that slow down a grid the most seem to be any sort of dynamic... property and making the grid large in terms of surface area. For example if to the right of the last column you have a lot of empty space, this seems to slow down the grid (I don't know how fox managed this one.) My resolution is 1152x864 and if I make a grid (or a browse) maximized, it is many times slower than a smaller version of the same thing.
>>>
>>>HTH,
>>>Peter
>>
>>I wouldn't agree that dynamic properties will slow down a grid. Actually, VFP is smart enough (I believe) to check just visible area of recordsource (6-8 rows) and doesn't go beyond.
>
>True it only redraws the visible space, but it still calls the dynamic properties alot. And it calls the dynamic properties more than you might think. I found that the DyanmicCurrentControl property is called for each line that is visible (when sparse is true) because if Dyn...Control returns a container or a button that cell needs to be empty if not currently on that cell or the container or button if on that cell. I like the dynamic properties, I just try to use them as little as possible to minimize the performance hit. ;-)
>
>Peter

If you agree that is called for visible part only, then what are you worrying about? Do you want to say that firing couple lines of code 6-7 times will visibly slow down the process? Of course, it's possible to write some extremely bulky code which will do the job, but ... it's our responsibility as developers to find better solutions.