>>< smirk > Don't let users edit in grids period. Eliminates any chance of confusion, and doesn't matter what my mouse pointer does over a grid =D)
>
>Agreed. I have only a very few instances ( really only one ... I try to never say never :-) ) where I have in grid editing and it's a special case. My concern is only for possible confusion for the user. If they see the arrow change to an I-beam, they'll probably just think they should be able to edit the field. Tsk-tsk ... shame on them. :-)

I think we're also getting into the area of Windows standards here. It should be an arrow for non-editable grid columns, and an IBeam for editable columns. Also, we do have situations where users MUST edit certain columns, it's quite beyond my control as a developer. We can try and recommend our standard of no grid edits, but users have certain interface needs where it really does make sense to edit a column occasionally, though not often - it's usually only one or two columns in any particular grid...

Another note: the Jim Booth method does not work under NT for me. It causes a "ghost" pointer that looks - you guessed it - "ghastly" :) Still trying other ideas...