>>>As Janis points out, nulls in and of themselves do not cause errors. Not handling them properly causes errors.
>
>Errors can occur in code where NULL's exist that could have not occurred had NULL's not existed. That's not disputed.
>
>NULL's really add no appreciable value. That might be disputed, but there was some pretty good code written before NULL's were on the scene, so we obviously can live nicely without them.
>
>If NULL's add no appreciable value (and in my judgement they don't) and can cause problems then my practical nature tells me that it's a lot more efficient to live without them, so I do.
>
>The question isn't can you deal with them.. rather it's why bother when you don't have to?

Question:
Table with fields for Name, Age.
What do you put in the Age field when you don't know the age?