>>>Consider a table of people with a logical sex field, where .T. is considered female and .F. male.
>>
>>Just wondering: is there a reason you *don't* want to use a numeric value? I think the issue of gender is not a boolean construct, but rather one of two equal choices. The concept is harder to understand when using a logical.
>>
>>Just my $.02
>
>Agreed. The way I deal with this is make sex a 1 wide char field, and in the interface make the choice from a list box. You could even make it a two column list box Showing Male,Female and in the second (invisible and bound) column, have the M,F.
>A boolean field for sex is an awkward construction that makes for awkward implementation.

I strongly believe that 2 option buttons are the best control for this purpose. I am not so strongly attached to the idea of using a logical field, but wouldn't it speed things up a little? The code for making the option buttons work with the logical field was not complicated. It was typical code for any control not using its .controlsource property.