>>In switching the VFP9, I now am getting quite a few FIELD fieldname DOES NOT ACCEPT NULL VALUES. This is obviously in the INSERT and APPENDS. Do we have to redo all the table definitions to allow NULL values? Was there not the concept of NULL values in VFP6? Trying to understand what was inserted in VFP6 vs what would happen if I allow NULL values to be inserted in VFP9.
>>
>>Thanks
>>
>>Brenda

>I think it's just a difference in SET NULL setting between VFP6 and VFP9. >Set it to OFF if you want the existing behavior.

SET NULL OFF says that all columns in tables will not allow null values by default. It is just a short cut way of not having to specify NOT NULL for each column during a table create. I still get the FIELD fieldname DOES NOT ACCEPT NULL VALUES error on my append. If I SET NULLS ON, then I will not get the error, because the field allows NULLs, but nulls will be inserted into the table. I am trying to determine what the consequences of having NULLS in my table might be considering that no where in my application do I check for NULLS.

Brenda