>>In my opinion it is more than OK. I prefer no NULLs (unless a compelling reason to do so) and all columns with defaults ( makes inserts a lot easier as well )
I did that in my VFP days, but with .NET I've stopped using the defaults in the SQL table and I set the default values in the code.
When I add a row, I call a function that loops thru all the columns in the datatable, and based on the type, sets the default values in the datatable row.


Why?

A. I had some problems a few times with the constraints created by the default values when handling the tables in SQL
B. I kept forgetting to do it when I added columns and sometimes I put the wrong values in.

The function never misses a column or sets the default incorrectly.