Oh. Not sure why you brought it up then.

From my perspective, the only real problem here is that when the grid doesn't have the focus, you can't tell which records are visible. As far as I know, you can't tell which record is the top record unless the grid has focus. My solution for this was to activate the first cell in the grid. I thought this a minor inconvenience.

There's also a minor problem in that the column's MouseMove event doesn't fire for the cell that is currently active -- it fires for the textbox within the column. My solution for this was to always move the active cell to either the first or second column. Since I don't use grids for input, this is also a minor inconvenience for me. No doubt the code should check to see if the mouse is over the active cell, and only then move to a different cell.

I also note now that the grid's MouseMove is always invoked -- for my purposes, since I use BindEvent to bind all of the columns' MouseMoves to a method in the grid, perhaps this second problem could be avoided altogether.

Jim




>>Naomi --
>>
>>I'm not sure why you didn't complain as well about the interface in your reference.
>>
>>Doesn't it always uses .ActivateCell, making the record under the mouse the current row? It also doesn't seem to try to put it back to where it was.
>>
>>Finally, it's called repeatedly for each MouseMove -- which may be significant if you're doing something other that setting ToolTipText.
>>
>>Jim
>>
>
>I did complain. I do remember I tested this approach, tried to optimize it and then discharged it.