#ADD TA TAG METADOCTOR CODE#
This means that if the parameter ends up being set in code to null under some conditions. Something along the lines of: CREATE PROCEDURE DATETIME = INT = NULL, The solution that i prefer is to default the stored procedure parameters to NULL (or whatever value you want), which was mentioned by sangram above, but may be missed because the answer is very verbose. I thought i would elaborate on some solutions to this problem that i have found useful for the benefit of people new to this problem. This issue is indeed usually caused by setting a parameter value to null as HLGEM mentioned above. WHERE TABLE_NAME = ' + trying to figure out what I'm doing wrong here.Įdit: As it turns out, Template was null because I was getting its value from a parameter passed through the URL and I screwed up the url param passing (I was using for and instead of &) SqlDataReader metadr = metaDataComm.ExecuteReader() įROM. MetaDataComm.CommandType = CommandType.StoredProcedure SqlCommand metaDataComm = new SqlCommand(sqlCommString, sqlConn) SqlConnection sqlConn = new SqlConnection(connPath) net's data connection to sql (), even though I am supplying the parameter. This is happening when I call a Stored Procedure with a parameter through. Procedure or function 'ColumnSeek' expects parameter which was not supplied. I'm getting the error when accessing a Stored Procedure in SQL Server Server Error in '/' Application.
0 kommentar(er)
