>>In practice it's equally useless, as you can't do anything with it - no operators work with those values. You can't say "if table1.bitfld1 OR table2.bitfld2" or any such thing - the stored values or variables with such values can't be used in boolean expressions, only in comparisons. Damn, even the 5K basic interpreter on ZX Spectrum, 36 years ago, was able to do "if x and y then".
>
>Even with boolean values I've grown into the habit of adding = .T. or = .F. , so to me it does not matter. I could not care less.

So you prefer to write "if a=1 and b=1" as it's much faster, more readable and easier to maintain than "if a and b"? :)

>BTW, thanks for your present. I'm sure it will taste well.

You're welcome. Next time we'll pick someone else for transportation, perhaps you or me :).