Not a problem. But I actually decided to change the field name anyway; it is "is_active." (similar to what you suggested). The type is C(1) and the values are "Y" or "N". So the field name and the value tell it all.

>You're right, I needed to wash my glasses.
>
>>I looked through the list of Reserved Words (in VFP help) and don't see Active on the list (Activate, yes, but not Active). Where did you see this word as a reserved? Thank you.
>>
>>>I strongly recommend that you DON'T use "reversed" boolean logic, there is no gain, and even you as the programmer will sooner or later get confused. Since Active is a reserved word, I recommend Isactive or Lactive as field name. If you use DBFs, you should also add a binary index tag to this field.
>>>
>>>>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?