>Oh. Not sure why you brought it up then.

Just as a sample an evolution of ideas.
>
>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.

As I said, this problem is solved using Dynamic properties of the grid. I don't remember if I ever posted that code here :(

>
>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
>