Thanks,

I know totally see your point i think.
You have set me to testing the things and i now now that there is a very simple solution to this.

But i agree that if you set the mousepointer property of a object to something different that it should be reflected in the whole column. In any way, it should be so when the sparse property is set to .f.
But that's my opinion. It looks like M$ has another opinion.

Thanks again,


>>First of all, i didn't want to bother you.
>
>You didn't "bother" me, :-) but it seems we might not have been accurately communicating or there were some missing details.
>
>>if you read all the messages you see that we also conluded that the things you do at desing time only affect the cell if it is active. But that can you set at design time. You don't need to set it to the same value every tim you come over the control.
>>But about the column, then you are right.
>>But if you set the mousemove code only in the columns mousemove event it will already work.
>>You don't need to set it in the grids mousemove event, or in the headers mousemove event.
>>
>>I thought it was more difficult. Thanks for directing me to that simple solution.
>>
>>I now think the solution is this.
>>At design time set the mousepointer property to 1 for all the controls in the column.
>>In the column's mousemove event set the grids mousepointer to 1 (this.Parent.Mousepointer = 1)
>
>Personally I think it's totally worthless that the mousepointer setting only affects the active cell ... doesn't seem to be much good to me, but others may disagree and have use for it. :-)
>
>Basically I posted the code to show that by judicially using this kind of code the desired effect can be achieved in a cell, column, header or grid itself depending on the specific need at the time. But the developer will have to use the right choice of code ( or none ) in the right place and some experimentation might be needful to get the desired result.
>
>At any rate, this kind of dialog is good for clarification.