cursor type: opening access parameter query using ado command

hi, i have a situation here.

i have created parameterized in my access data base, and i have successfully run the query and get the result return to my recordset object by using ado command object.

the matter is, the recordset cursor type is adOpenFowardOnly which prevent me to move around the recordset, and once the recordset is open/set, the cursor type cannot be change anymore.

the question is, how can i retrieve the recordset form query using ado command that have other cursor type and location?
LVL 13
khairilAsked:
Who is Participating?
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.

TravisHallCommented:
If you are using the Open method of your Recordset object to run the query, just specify a different CursorType (the third argument) when you call Open.

If you are using the Execute method of the Connection object or the Command object, I think you will need to switch to using the Open method of the Recordset object instead. These methods simply use the default cursor type, a forward-only cursor.

You are correct when you state that once the recordset is open, you cannot change its cursor type. That is why you must specify the cursor type as you open it, not afterwards.
0
khairilAuthor Commented:
yes it is true if i'm using the open method...  but because i'm using the ado command, the open method is not invoke, it is like this (some portion of code):

'==================================================
set prmAge = cmdPerson.CreateParameter(<My Parameter Name>, <type> ....)

prmAge.Value = 34

cmdPerson.Parameters.Append prmAge

set rsPerson = cmdPerson.Execute
'===================================================

there is no way i can set cursor location during set. if i set it before invoking set command, all the setting will reset. any idea?
0
TravisHallCommented:
khairil,

You have not used the Open method of the recordset object in that code. If you don't see ".Open" anywhere in your code, you haven't used the Open method.

In case you are not aware, "method" is a technical term, meaning a procedure which is a member of an object.

You have used the Execute method of the Command object. You will need to switch to using the Open method of the Recordset object.


Dim rsPerson As Recordset
Set rsPerson = New Recordset
rsPerson.Open "some SQL", cn, adOpenStatic

where cn is your Connection object and substituting something appropriate for "some SQL".

Yes, you will need to know a tiny bit of SQL to get this to work. Maybe I can help you with that, if you provide me a bit more information about your query.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Anthony PerkinsCommented:
As Travis has mentioned, you need to use the Recordset Open method.

What you are overlooking is that the Source for the Recordset Open method can be a Command object, so in your case, first set up your Command object as you have done already:

set prmAge = cmdPerson.CreateParameter(<My Parameter Name>, <type> ....)

prmAge.Value = 34

cmdPerson.Parameters.Append prmAge

Then comment the next line as not needed
'set rsPerson = cmdPerson.Execute

Set rsPerson = New ADODB.Recordset
With rsPerson
   .Source = cmdPerson
   ' If you are using a connection object (cn) than comment the next line
   .ActiveConnection = "your connection goes here"
   'Or if you are using a Connection object (cn) then uncomment the next line.
   'Set .ActiveConnection = cn
   .CursorType = adOpenDynamic 'or whatever
   .LockType = adLockOptimistic
   .Open Options:=adCmdStoredProc
End With

...

rs.Close

Set rs = Nothing
Set cmd = Nothing
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
TravisHallCommented:
khairil,

You have not used the Open method of the recordset object in that code. If you don't see ".Open" anywhere in your code, you haven't used the Open method.

In case you are not aware, "method" is a technical term, meaning a procedure which is a member of an object.

You have used the Execute method of the Command object. You will need to switch to using the Open method of the Recordset object.


Dim rsPerson As Recordset
Set rsPerson = New Recordset
rsPerson.Open "some SQL", cn, adOpenStatic

where cn is your Connection object and substituting something appropriate for "some SQL".

Yes, you will need to know a tiny bit of SQL to get this to work. Maybe I can help you with that, if you provide me a bit more information about your query.
0
Anthony PerkinsCommented:
That last line should have read:
Set cmdPerson = Nothing

Anthony
0
TravisHallCommented:
Whoops, sorry about the duplicate send.

Gakk! Of course, acperkins is quite correct. When I said you need to know some SQL to get this to work, I forgot that you can just use Command object as the source. I don't think I have ever used that in production code, so I had forgotten about it, but I did try it out once just as a test.
0
khairilAuthor Commented:
hi all,

actually by the time i read the answer i have found the solution for my problem, actually at first i thought it must be a ado connection object at source property during recordset open command. after reading most of the msdn articles, i came across a sample which using a ado command as it source.

so instead of:
rsPerson.Open <my connection>,....

i can use:
rsPerson.Open <my command>

acperkins just give me other way to open the recordset that why i vote for it.
0
TravisHallCommented:
Generally, you'd be wanting to use your Connection object as the second argument to the Open method, and either a Command object or a string containing SQL code as the first.

acperkins gave the correct solution, so of course you were correct to accept it.
0
khairilAuthor Commented:
thank you to you all... :)
0
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
Visual Basic Classic

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.