Re: Executing a StoredProcedure using ADOCommand object in ASP.NET
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Thu, 7 Dec 2006 22:46:41 +0000 (UTC)
MJ (MJ@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
I would love to port the app to a .net application but the client
does not want to do that they just want to change the extension from
.asp to .aspx and fix the issues that occurred because of the change.
OK, I got fooled by the declaration of an OleDbAdapter, but you don't
seem to use that one.
Still, I have one more suggestion for modernization. :-) Judging from
your error message you are using the MSDASQL provider, that is OLE DB
over ODBC. Not that I am certain that the problem would go away if
you change
Driver = {SQL server}
in the connection string to:
Provider=SQLOLEDB
or even
Provider=SQLNCLI
but at least you would get somewhat better performance.
Really what is going on in your code, I don't know. What is the name
of the stored procedure you are trying to call? Does it have any
"funny" characters in the name?
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
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
.
- References:
- Executing a StoredProcedure using ADOCommand object in ASP.NET 2.0
- From: MJ
- Re: Executing a StoredProcedure using ADOCommand object in ASP.NET 2.0
- From: Erland Sommarskog
- Executing a StoredProcedure using ADOCommand object in ASP.NET 2.0
- Prev by Date: C++ connection to OleDbConnection
- Next by Date: problem in inserting the data in sqldatabase .adp file
- Previous by thread: Re: Executing a StoredProcedure using ADOCommand object in ASP.NET 2.0
- Next by thread: Connect to XLS through ADO - Field names not coming through
- Index(es):
Relevant Pages
|
