Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
leedar
Starting Member
3 Posts |
Posted - 2005-05-31 : 13:44:17
|
| I have a 'proc A' being called from asp.that will call another 'proc B' which will call 'proc C' ( 2 to 4 times depending on some paramters passed to 'proc A'). if I execute the stored 'proc A' from query analyzer it works fine. if I execute through asp, the profiler shows the following 2 entriesexec procA 'param1', 'param2'select * from exec procA 'param1', 'param2'and will fail from asp.I am calling 'proc A' only oncewhy is the profiler showing 'select * from exec procA 'param1', 'param2' call which I am not makingThanks '. |
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2005-05-31 : 13:55:29
|
| >> why is the profiler showing 'select * from exec procA 'param1', 'param2' call which I am not makingThere must be a logical explanation...Maybe it's just pulling Your leg ?Probably You have to set the command type to adCmdStoredProcedure , create parameters etc...[url]http://www.asp101.com/articles/wrox/asp30/26100903.asp[/url]rockmoose |
 |
|
|
leedar
Starting Member
3 Posts |
Posted - 2005-05-31 : 14:02:23
|
| I am using Set objHeaderRS = objCN.Execute(strSQL) |
 |
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2005-05-31 : 14:39:02
|
| What is the value of strSQL at this point in the code ?rockmoose |
 |
|
|
leedar
Starting Member
3 Posts |
Posted - 2005-05-31 : 14:47:27
|
| exec procA 'param1', 'param2'I did response.end right after the executesql statementit failed, so executed the above line in query analyzer, it worked, but profiler shows another statement after this which I dont have in code |
 |
|
|
|
|
|