>I maintain that a pair of option buttons are more appropriate for >displaying a field storing two equivalent logical conditions. We don't >want a control like a checkbox which seems to say "female" or "not female". >I have never seen a paper form that looks like that. You should see a >clear choice of "male" and "female". Yes, in this case having both words on screen is more clear to the user (though it involves the complicacies described upstream in this thread). I've had to develop a checkbox with variable caption (works in FPD2.6, too) for some cases where having a checkbox next to text is simply not enough - for instance a series of checkboxes for defining various yes/no choices; having the "yes" next to a checked box, and "no" to an unchecked made it more clear (in that case). Other case was when the caption tended to be ambiguous (English is rather noun-oriented, Serbian is more verb-oriented, hence the difference in approach), I've had to make very clear sentences, like "has heating", "has no heating", because putting just "heating" could mean "wants heating" (it was an app for a real estate agency). Besides, the effect of changing caption is visually more catching than (dis)appearance of the check mark.