Questiondefault value or passing optional parameter to stored procedure using DAAB ? please guide and help

I am using DAAB with stored procedures. I use stored procedures more then once if possible. If I add a parameter later in stored procedure, I have to supply value for this in functions where it is even not being used as well, other wise it shows an error
that number of parameters are not same.

is there some solution for this ?

Or please guide is there some if I add parameter in last of parameter list in stored procedure and set a default value for it and I may have not to provide value for this from functions where I am not using it.

Can you please try the solution of implementing a optional parameter in your stored procedure as described in this blog. http://weblogs.asp.net/stanleygu/archive/2010/02/08/solution-5-implementing-optional-parameters-in-t-sql-stored-procedures.aspx

It fails because the overload you used for ExecuteNonQuery explicitly compares the number of parameters you passed and the number of parameters the command should have. The way to accomplish the behavior you want is to create a DbCommand object first,
add parameters to it, and call ExecuteNonQuery against the Database object passing the DbCommand object.