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.
FWIW, using logical fields in VFP does not add much. Numeric fields work fine with form objects and SQL is still easy.
Regards
JR
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
