>Sergey
>
>>>REPLACE FOR ISBLANK(eclrhse) eclrhse WITH Null
>
>Should work well with local tables... but nulls in a logical field have significant ramifications for upsizing.
>
>Bit fields in SQL Server do not allow NULL. This means you'll have to alter the field type if you ever need to upsize.
>
>My advice would be to do as others have suggested, use a character field or a one digit numeric field. Both upsize well.

First, where in my messages did I suggested to use one type or another? Second, nobody forces you to use the bit type, use tinyint instead.


>FWIW, using logical fields in VFP does not add much. Numeric fields work fine with form objects and SQL is still easy.

Where did I say otherwise or avocate using logical fields?

Sorry, but I don't undarstand what your whole post's about.