Boolean type fails

[Tim Davis]

Hi Ruslan,

>>>>   I've tried creating a new field of boolean type both with SQL on 
>>>> the
>>>> server and with VAPP. Every time it fail a diagnosis and causes
>>>> problems. The diagnostic said something about finding 1 (of 
>>>> something)
>>>> when it expect 2. My work around is to use a different field type. I
>>>> don't know if this has been reported before, but apparently I've
>>>> experienced it before, because I found byte fields used as boolean 
>>>> in
>>>> my tables.
>>>
>>> Do you use encryption?
>>> If yes, then diagnose is wrong.
>>> Your table is good.
>>
>> No, I'm not using encryption.
>
> Then I do not understand problem
> I use Boolean types very often,
> And at least VAPP works with them perfectly.
> Check all again on new fresh db.

Ok, I tried on simple new db no trouble.

Here's my experience:
I create a new field as boolean on server via sql. Problems started 
happening. I ran a diagnostic in VApp and it said the problem is with 
the new boolean field. I removed the field with VApp and recreated it, 
problems still existed. I removed the field altogether, diagnostic 
found no problems. I added the same field name but different field 
type, no problems in diagnosis or from use since.

Tim