danaanderson (5/25/2014)
Jeff Moden (5/25/2014)
danaanderson (5/25/2014)
I don't think that it matters about the position in the parameter of the dbtype spec, but I'll check it out. It is ASP.NET. Classic ASP is quite a different animal. In any case, from what I know this error is indicating that more parameters were sent than the procedure has receptors for...but it is ambiguous. I really wish T-SQL had a function like PARAMETERS() in VFP. I could know for sure.Anyone else have any thoughts? It's surprising that there was only one person replying in a time span of about 23 hours.
Dana
Heh... it IS an SQL Server forum with a large number of people that live in the United states and you've asked an ASP question on a holiday weekend. 😉
Well, it was SQL Server that was throwing the error. I thought it was the best place to start looking...and asking. True, though, it is a holiday weekend and most are probably out firing up the barbie.
Dana
Ah... understood. I noticed that you marked the post of JLS as the answer so I went and looked at the post he provided a link for. It would seem that some form of "read only field" was the problem and you needed to change the parmeter listing of at least 1 of the fields from "bind" to "eval". If that's true, which of your fields was it and was it an "IDENTITY" or "COMPUTED" column or ???
I'm asking because the code is automatically generated based on the stored procedure parameters and seems like it could be a common problem. Since SQL Server produced the error, I thought I'd ask for more details on what you did for a fix so that folks like me that know little of ASP can lend a helping hand in the future.
Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.