>Are you adding records to the view with APPEND BLANK? If so you will get BLANK values (i.e. 0 for a numeric field) instead of the .NULL. you might expect. You have to either specify the .NULL. programmatically, or use a default in the view.
>
>This is one of those cases where VFP doesn't behave like SQL server (which will insert .NULL. for all blank values) but probably should. It's probably this way because DBFs got NULL support late and assuming .NULL. might break a lot of older apps.
>

It seems a welcome addition to VFP would be APPEND NULL which would append blank or null, depending on the table's properties - null in all the fields that accept nulls.