General information
Title:
Inserts, SQL and Nulls
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
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only