I have had this happen before as well. I had to actually adjust the stored procedure to handle a return code and a return message. Then in the stored procedure I had it test each parameter and return a 1 if it failed and a 0 (at the end) if it succeeded. Actually I have that on all my stored procedures now. It has not added any measurable amount of processor time and some of my procedures take up to 30 parameters

The other work around is that set the parameter = null in the stored procedure. Then just add parameter to your command setup in your program but don't assign it a value or assign it a default value.

Good Luck,

D