Since you're willing to set the form prop to .f. if the table value is .null., it sounds like you never really need the .null. state so can't you force the .null.'s to be .f.'s when the view builds the cursor? (He said, naively, not knowing too much about views). If it's a huge table, or a remote table you don't own, or something like that, I could see why you couldn't do this. But if it's your local table, why not just force all the nulls to be f's once and then make sure it defaults to f as new records are added?

>Hello,
>
>I have a checkbox whose control source is a logical (or numeric) field in an underlying view. (1) If the value of the control source is .f. -- then no check mark (OK), (2) if the value is .t. then a dark check mark shows up (OK), (3) if the value is .null. then a 'greyed out' check mark appears -- weird?
>
>I can work around it by making the control source a form property and then setting the form property to .f. if the table value is .f. or .null., but I was just womdering if anyone has seen this behaviour and is it considered a bug? (VFP 5.0a)
>
>Kevin