>>My favourite candidate to look for when a grid is slow are the dynamic properties. If any of them is a method or function call, just try to make it a simple expression or comment out the code where you set it. I've seen incredible differences in speed when I replaced a method call which returned a rgb() for a dynamic backcolor with a field which contained that rgb value filled in advance. Keep in mind that for each refresh, each dynamic property gets evaluated for each visible cell.
>
>I think your suggestion doesn't apply here. The hourglass I'm referring to appears when I click on the Header of the column. I do not use any dynamic properties for the grid at all (though I didn't check the parent class code closely). The cGrid grid behaves normally, while my grdSorting produces that weird behavior. I posted all the code in the begining of the thread. I made a small change to use a reference to last clicked header rather than clearing pictures in all headers. It didn't make a difference, may be even worsen the situation.

The code looks right... except that I'd rather have a custom property in the column which would keep the name of the index tag to apply to that column if its header is clicked. Something that can be done in grid's init. This way you avoid looping through the available tags to find out which one to apply. At least that's how I did it last time.

What can I say? Fire up the coverage logging in the beginning and shut it off in the end of the headerclick method, and then analyze it in coverage profiler and see what sort of code is eating the cycles.