M
Martin Widmer
Hi guys!
I get this message when trying to insert a new record into a datatabel which
is part of a dataset connected within VS 2005 (VB) from a datagridview
control via a DataTableBindingSource and TableAdapter to an SQL Server. In
the SQL server the field is declared as "do now allow null", BUT I put the
getdate() function as default value so the field should be automatically
filled with the current date.
So why do I get that exception up there? Does SQL server test for NULL
actually BEFORE inserting the default value? That would be rather stupid,
wouldn't it?
When I insert the record manually via the server explorer, the error does
not occur.
Martin
I get this message when trying to insert a new record into a datatabel which
is part of a dataset connected within VS 2005 (VB) from a datagridview
control via a DataTableBindingSource and TableAdapter to an SQL Server. In
the SQL server the field is declared as "do now allow null", BUT I put the
getdate() function as default value so the field should be automatically
filled with the current date.
So why do I get that exception up there? Does SQL server test for NULL
actually BEFORE inserting the default value? That would be rather stupid,
wouldn't it?
When I insert the record manually via the server explorer, the error does
not occur.
Martin