Handling DBNull When Inserting or Updating Using Stored Query

Hi Guys,

I have a question and I'm hoping someone can help me sort out a clean and effective way of handling my problem.  Most of the fields in my primary table are not required and thus allow nulls.  Controls in VB don't return DBNull