No, that line refers to programmatic access to your database.
Here's how it works. Like I said, there are subtle differences in the way these properties are behaving. Null and a zero length string are not really the same:
Required No
Allow Zero Length Yes
Both will work:
Code:
oConn.Execute("INSERT INTO MyTable (MyColumn) Values('')")
oConn.Execute("INSERT INTO MyTable (MyColumn) Values(null)")
Required Yes
Allow Zero Length Yes
This will work:
Code:
oConn.Execute("INSERT INTO MyTable (MyColumn) Values('')")
but this won't:
Code:
oConn.Execute("INSERT INTO MyTable (MyColumn) Values(null)")
Required Yes
Allow Zero Length No
Now both lines will fail, because the field is required and cannot be an zero length string
Required No
Allow Zero Length No
This is the opposite of No / No. That is, this will work:
Code:
oConn.Execute("INSERT INTO MyTable (MyColumn) Values(null)")
but this won't:
Code:
oConn.Execute("INSERT INTO MyTable (MyColumn) Values('')")
Because the field is not required, you can insert null. However, you can't insert a zero length string as the field does not permit that.
Null is not considered the same as an empty string. An empty string is a string with zero length, while null is undefined.
Confusing, don't you think?
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.