>>I agree with you and I agree with Tore. This "reversed" logic would be a maintenance head ache and support head ache. So I decided (even though initially I didn't think I would) to go with Bill Fitzgerald's suggestion. I have changed the field type from logical to C(1). It looks like it is all around better solution. The Char type fields are easier to deal with in terms of setting default in the db container. And Stonefield Query gives me better options to work with C field.
>>
>>Thank you for your input.
>
>If you implement more options than !empty() via the char field, you are already well along the slippery slope of magical constants -
>the usual remedy being a lookup table with text and perhaps logic to be balanced against existing fwk support and update frequency.
This particula field right now will have just to values, 'Y' and 'N'. The database default will set the value 'Y' and user could change it to 'N'. That is all.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
