eramgarden
Programmer
I get this error:
Operation is not allowed when the object is closed.
on this line of code:
set rsADO = oSvy.GetCaller(callid,incid)
When I point global.asa to my local database. But, when I point it to Production database, it works fine.
These are some info:
1. I have the callid and incid hardcoded in ASP page for testing
2. I looked at the VB dll and it calls a stored proc. I ran the stored proc by itself with those hardcoded values and it does return a recordset on my local database.
3. Google had it to use "SET NOCOUNT ON" in stored proc, I did that but still got the error.
4. I checked the order of calling the stored proc from Vb dll and it calls the stored proc correctly.
5. compared the stored proc in Production to the one on my machine and they look the same.
6. This is the VB code that causes the error:
SQL = "GetCaller '" & callid & "', '" & incid & "'"
errorClass = "ExecDBcnx1300"
Set rsADO = DBCnx.Execute(SQL)
Set GetCaller = rsADO ' return the recordset
7. This is the ASP code:
set oSvy = Server.CreateObject ("SurveyAPI.DisplaySurvey"
if Err then
Session("DCS_ErrorDesc"
= Err.Description
Response.Redirect "error.asp"
Response.End
end if
set rsADO = oSvy.GetEspCaller(callid,incid)
What am I missing? how could this work on one datbase and not on the other???
Operation is not allowed when the object is closed.
on this line of code:
set rsADO = oSvy.GetCaller(callid,incid)
When I point global.asa to my local database. But, when I point it to Production database, it works fine.
These are some info:
1. I have the callid and incid hardcoded in ASP page for testing
2. I looked at the VB dll and it calls a stored proc. I ran the stored proc by itself with those hardcoded values and it does return a recordset on my local database.
3. Google had it to use "SET NOCOUNT ON" in stored proc, I did that but still got the error.
4. I checked the order of calling the stored proc from Vb dll and it calls the stored proc correctly.
5. compared the stored proc in Production to the one on my machine and they look the same.
6. This is the VB code that causes the error:
SQL = "GetCaller '" & callid & "', '" & incid & "'"
errorClass = "ExecDBcnx1300"
Set rsADO = DBCnx.Execute(SQL)
Set GetCaller = rsADO ' return the recordset
7. This is the ASP code:
set oSvy = Server.CreateObject ("SurveyAPI.DisplaySurvey"
if Err then
Session("DCS_ErrorDesc"
Response.Redirect "error.asp"
Response.End
end if
set rsADO = oSvy.GetEspCaller(callid,incid)
What am I missing? how could this work on one datbase and not on the other???