G
Greg
We have been using the same sproc for an insert for quite some time. The
sproc create a new key for the record to insert, uses the key for the insert
and then has an output param for the key. The key field in the DataTable is
'names_id'. The is the sourcecolumn for the sql output param.
Yesterday, one of our developers added an insert trigger to the table the
sproc inserts into. Now, we are getting an exception that state 'name_id'
cannot be Null. Very strange as his usually suggests to me I am passing in
a parameter that is NULL. Well, names_id is not a param to the sproc. It's
the source column for the sql output param.
I am new to triggers so I have no idea what introducing the trigger has
done. Anyone know what the source column for an output param would all of a
sudden be NULL? Strange thing to is I no longer see the sproc running in
SQL Profiler.
sproc create a new key for the record to insert, uses the key for the insert
and then has an output param for the key. The key field in the DataTable is
'names_id'. The is the sourcecolumn for the sql output param.
Yesterday, one of our developers added an insert trigger to the table the
sproc inserts into. Now, we are getting an exception that state 'name_id'
cannot be Null. Very strange as his usually suggests to me I am passing in
a parameter that is NULL. Well, names_id is not a param to the sproc. It's
the source column for the sql output param.
I am new to triggers so I have no idea what introducing the trigger has
done. Anyone know what the source column for an output param would all of a
sudden be NULL? Strange thing to is I no longer see the sproc running in
SQL Profiler.