Hi gerry,

>The author of "Inside SQL Server", who is/was a key person on the Server development team, advises to avoid NULLs if at all possible. As I migrate my app to SQL Server, I see this as another reason to take his advise ...

I don't understand from which perspective he does reccoment this. From the perspective of MS SQL's shortcommings or problems that come with database design?

If we look at database design there often is no way arround NULLS. In SQL Server there is no such thing as blank dates we use in VFP. NULL dates are the only option here. Also, in ither cases where information is missing, you might find there is no way you can avoid NULLS. a NULL is different from a zero. So if in a scientifical application you have to store measurements you might find yourself in a position where you have to make a distinction between 0 and NULL.

>Ever load a NULL into the ControlSource of a TextBox ? Don't ... because the field becomes inaccessable; ie. you can't type over / into it. It won't even focus. Useless in a data entry situation where one is trying to "update" a null field.

What do you mean? If a textbox is bound to a field you can use nulls quite easily. I've not experienced the problem you outline here.


Walter,