>I know it's common practice in VFP to not allow nulls. I assume this is also the case in SQL server. My problem is that when I do an SQL INSERT to insert a blank record for editing, any field left 'blank' is actually null filled and the insert fails. Two solutions come to mind. 1. Set a default value for each field in the SQL table (or VFP remote view). 2. Cycle through the record checking for nulls. Is there a better way? Should I allow nulls?
>
>TIA
>
>John

John can be common practice when you where developing old fox applications now is not that common if the fields are optional then you should let them be null.