Dmitry,

Not sure if this helps that much but I have seen a field like this named INACTIVE. At least it takes the word 'NOT' out of the field name.

-Dan

>Hi,
>
>I am adding a field to the parts file that will allow user to check some parts as Active and some as Not Active. On the screen it will look very clear and unambiguous. The field (logical) will have default as .F. and named NOT_ACTIVE. When creating reports the user will use this field in the Stonefield Query named PART NOT ACTIVE. And if they want to include in the report only NOT active parts they will specify it as "PART NOT ACTIVE is True." Do you think that average user (person) will not be confused by this "reversed" Boolean logic?