>> >> >In a grid i use a check field to mark some item on, and some text
>> fields.
>> >> >When i switch the grid READONLY it is 'normal' that the user cannot
>> change
>> >> any values in the text fields, etc...
>> >> >
>> >> >Why can i still change the check field ??
>> >> >
>> >> >I there any way to so that the user cannot change it any more ?
>> >> >
>> >> >Help please.
>> >> >
>> >> >
>> >> >Thnks... Marc
>> >>
>> >> By MS design check box doesn't understand ReadOnly property, so you
>> should
>> >> use Checkbox.Enabled=.F.
>> >
>> >... but this leaves the Checkbox looking disabled, while the rest of the
>> >controls look enabled. My preference is to have RETURN .F. in the When.
>>
>> What do you mean saying 'looking disabled'? You can always customize
>> DisabledBack/ForeColor properties to get necessary look. BTW, When and
>> Valid property are legacy ones and not recommended to use.
>
>Yes you can adjust those properties, but my preference is not to. This
>allows me to have a global colour change control, or to set the colours
>in a class library, and not worry about this one (or 10 or 100) instance
>of the control.
>
>Yes, When and Valid are legacy. But, IMHO, they are the most suitable
>in this case. All of the applications that you bring from FP26 to VFP
>should be rewritten, and this will likely hold true for VFP5 to the next
>couple of versions, so I don't place much weight in the argument that
>these are legacy.
>
>/Paul

Moving from 2.6 to VFP you can never meet Grid with CheckBox with When snippet, so what the necessity to hold things down adding a snippet which be a pain for next upgrades. BTW, you can get into more troubles with existing grid if a client will request flexible functionality (not always Read-Only checkbox) and will add more code to When event again.