ActiveConnection property error...0x800A0E7B or Syntax violation error :0x80040E14

I am using cursors on my stored procedures. On the asp side, i use a Visual Basic Dll containing the following code for the database connection..

Function sp(ByVal SP As String, ParamArray params() As Variant) As ADODB.Recordset
    Dim rs As ADODB.Recordset, cmd As ADODB.Command
    Set rs = New ADODB.Recordset
    Set cmd = New ADODB.Command
     cmd.ActiveConnection = ...
    cmd.CommandText = SP
    cmd.CommandType = adCmdStoredProc
'note : if i change this to cmd.CommandType = adCmdText then i get the syntax error message on the asp page:
'(0x80040E14)Syntax error or access violation

     collectParams cmd, params
    rs.CursorLocation = ...
    rs.Open cmd, , adOpenForwardOnly, adLockReadOnly

    Set cmd.ActiveConnection = Nothing
    Set cmd = Nothing
    Set rs.ActiveConnection = Nothing

'return the damn recordset :(    
Set sp= rs
End Function


Now in many cases i have seen that when i use the dll to run my stored procedures and return recordsets, the page breaks and i get the following error:
 (0x800A0E7B)
Cannot change the ActiveConnection property of a Recordset object which has a Command object as its source.

or

Syntax error or access violation..

I get stuck on this error .. and in most of these stored procedures, I use either multiple select statements (not to return values, but to assign inner variables..)
for example : i use the following in a cursor..

set @Exists = (Select @myvar where @myvar in (Select myvarfield from [tablename] where <condition>
                  Inner Join table1 ON <condition>))

Query analyzer returns perfect values, but only my asp page breaks..and i have really got fed up of this error..have almost become paranoid of it ..

help me fast...please..SOS
DeEl In ThE DiGiTaLL WoRlD

digitaleelAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

wsteegmansCommented:
I think this line occurrs the problem.

    Set cmd.ActiveConnection = Nothing
    Set cmd = Nothing
    Set rs.ActiveConnection = Nothing       <-----------------

You already set the ActiveConnection to nothing by doing this:
    Set cmd.ActiveConnection = Nothing

Because the recordset uses a command object, it has no active connection, the command object does. So, when you set the ActiveConnection of the Command to nothing, you doesn't have to do it again for the Recordset.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP

From novice to tech pro — start learning today.