Hi, Ron: Also, I often use two different but similar number field techniques:
fieldname_bit = a number field with a required value, being 1 or 0 (defaulting to one or the other). fieldname_pip = a number field with a value of 1 or empty (defaulting to one or the other). There are occasions when the latter is simpler, so long as nothing else in the database depends on this field having a value. Of course, there are also cases where you want a "yes/no" text field, which is much "friendlier" to the user, but can't be used directly in a boolean operation. This field sometimes requires formatting with a "Yes/No/Unknown" value list instead. That may be the case if a field must have an entry and the user is unable to make a proper determination. The default could be "Unknown," or could be blank if you want to force the user, through field validation, to focus on this field and enter "Unknown" if they don't have an answer. Except for fieldname_pip type fields, null is not allowed. -- E >>What do most developers do for a field that should be Yes/No, since there is >>no Boolean data type? >>FM 8.5 >>Ron -- Erik Wegweiser / Intelligent Database <http://www.intelligentdb.com>. P.O. Box 88, Allston, MA 02134 (Boston, U.S.A.) Tel: 617-965-9544 / Mobile: 617-899-9090 Member, FileMaker TechNet, FileMaker Business Alliance "What's on YOUR mind?"
