Wouldn't there be a risk of hard-to-diagnose problems if you do that? You could BROWSE or display the data and it'll look blank, but in the code it'll NULL values will still return .F. for EMPTY().

>I have had the same experience in VFP (not using NULL). This is why I love the command:
>

>SET NULLDISPLAY TO ""
>

>
>>So far I have worked with the Visual FoxPro Database. I rarely insert NULLs intentionally, they usually appear from the result of an outer join.