Greetings,
I have used such syntax as in this snip below:
So the adoCMD object, which I very much enjoy the syntax of that object type, as it automatically builds the ADO.Parameters objects for me when it detects the SP on the BE DB and I make the .Parameters.Refresh call.
Question... must I receive back a brand new adoRS object from the call to the .Execute() method? Or is there some other adoCMD syntax where I can provide the adoRS object I wish the SQL SELECT result set to end up in?
What lacks in allowing the .Execute() method to build the adoRS object is the ability to specify attributes of the adoRS object.
And no, I am not interested in using an interpretive loop code to transfer data out of the automatically provided adoRS object to my own adoRS object.
I am thankful,
I have used such syntax as in this snip below:
Code:
'Define attachment to database table specifics and execute commands via With block
Set adoCMD = CreateObject("ADODB.Command")
With adoCMD
.ActiveConnection = ObjBEDBConnection.ADODBConnectionObj()
.CommandText = "clsObjProductsTbl_LocateProductByID"
.CommandType = adCmdStoredProc
.Parameters.Refresh
.Parameters("@id").Value = Me.id
Set adoRS = .Execute()
End With
Question... must I receive back a brand new adoRS object from the call to the .Execute() method? Or is there some other adoCMD syntax where I can provide the adoRS object I wish the SQL SELECT result set to end up in?
What lacks in allowing the .Execute() method to build the adoRS object is the ability to specify attributes of the adoRS object.
And no, I am not interested in using an interpretive loop code to transfer data out of the automatically provided adoRS object to my own adoRS object.
I am thankful,