|
|
Posted by Erland Sommarskog on 12/02/06 23:17
jbonifacejr (jbonifacejr@hotmail.com) writes:
> Thanks Erland...I see where I screwed up. I thought I had explained
> what was wrong, but I did that in a different thread in another forum.
Posting the same question independently to two forums is not a nice
thing to. This means that people can waste time on answering your post,
when it has already been answered elsewhere.
> Anyway, I got this working using classic ASP and ADODB. Now I am going
> to try to get it working over ASP.NET and ADO.NET. Wish me luck.
>
> So far, eveerything works except that I am constantly being told that
> the stored procedure expects a parameter that was not supplied.
> However, The same two parameters are created and added to the
> Parameters of the command object.
Again, without seeing your code it's hard to tell. There is a difference
between ADO and SqlClient though: with ADO, the parameter names are
just local to the application, so if you misspell a parameter name,
you may get away with it. Not so with SqlClient.
> I'll continue to work on it and see if I can get it to work. Looks like
> I need a datareader or some other object.
Since your procedure has an output parameter, but no result set, the most
conventient method to use is ExecuteNonQuery, in which case you only need
the Command object.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|