What is the difference between 2 ways to create a RECORDSET ?

[eyal7773]

Hello,
I would like to know What is the difference between 2 ways to create a RECORDSET.

Until 2007 I used to create it like this :


--------------
Dim db1 As Database
Dim rec1 As Recordset
Set db1 = CurrentDb
Set rec1 = db1.OpenRecordset(strSQL, dbOpenDynaset
-----------------

But when 2007 arrived, I read Sams Elison book and then I started to create it like this:
----------------
Dim cnnX As ADODB.Connection
Set cnnX = CurrentProject.Connection
Dim myRecordSet As New ADODB.Recordset
myRecordSet.ActiveConnection = cnnX
myRecordSet.Open SQLstatement
----------------

WHAT IS THE DIFFERENCE ? is there one way that is more quick ? More efficient ?
Thanks.

[NoellaG]

Hi,

* first way is the "old" DAO way to address recordsets, I used it since access 2. Haven't took the time for access 2010 , but before that ADO was still the way to address recordset clones of forms.

* The ADO way is younger and more object orientated. I forgot in which version it was first available, but I guess Access 2000. In those days Microsoft told us in some conferences that in time they would stop supporting DAO, but it still stands I see.
Myself, as I like to use as much as possible object orientated code (I use a lot of class modules and my alltime favorite programming interface is Omnis studio) I mainly use ADO. I don't know if its faster though. Maybe someone else?

grNG

[ajetrumpet]

In those days Microsoft told us in some conferences that in time they would stop supporting DAO, but it still stands I see.

there again, DAO is easier for an independent developer to use, so MS is migrating away from it. I'm not sure, but if they stopped supporting DAO, I would bet that SQL migration numbers would start going up. Again, a swift way to earn cash.

[pbaldy]

My understanding is that DAO is better optimized for an Access (JET) back end, ADO for others (SQL Server, Oracle, etc). MS definitely started to move away from DAO with A2k, but we dragged them back.

DAO isn't going anywhere anytime soon. Likewise the pushes towards ADP and DAP were reversed. I think they have theories about what might work for the market and will start in that direction, but at the end of the day they will respond to market forces.

[ajetrumpet]

they will respond to market forces.

they have the most force Paul. in essence they ARE the force. Skywalker even learned his skills from them! Sad, isn't it?

And No, we haven't dragged MS back at all. I have to take the other side. Stopping the migration to macros would be a great example of how to accomodate the little guy's job security. But of course they're not interested in that.

[pbaldy]

I posted thoughts on macros in post 6 here:

https://www.accessforums.net/access/...ries-8112.html

By enhancing macros, they've added to toolbox, not diminished it. VBA is still there for anybody who wants to use it. Don't worry, the MVP's that meet with MS have your back there. They would scream if MS contemplated dropping VBA, and believe it or not MS does listen. Not saying they will always follow MVP advice, but they do listen, both to us and the market.

[ajetrumpet]

well that's good to know Paul. That is certainly one good thing that has come out of better corporate responsibility. If anything else, increased competition has made Bill Gates consider the quality of his programming department. We all know he can sell...