Prev: A Totals query problem
Next: Help with table design
From: David W. Fenton on 15 Jul 2010 19:04
The Frog <mr.frog.to.you(a)googlemail.com> wrote in
news:fb0c705e-e29c-4590-88a2-36e678fd7e70(a)j4g2000yqh.googlegroups.com
:

> Like David said, if the BE is MDB or an ODBC then I use DAO. If on
> the other hand I want to be able to talk directly to a server at
> some point in the future (scaling up) and really want performance
> then I tend to dodge ODBC connections and instead use ADO to talk
> to the database server directly.

In general, I would say that doing the latter means you're using the
wrong front-end development platform, as it means your app is not
bound.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
From: David W. Fenton on 15 Jul 2010 19:08
"Sven Pran" <no.direct(a)mail.please> wrote in
news:oJydnZaoBKSkRKPRnZ2dnUVZ87-dnZ2d(a)telenor.com:

> I am using ADO and didn't know about DAO at all, so I used Google
> to find some information. What I found on Wikipedia was among
> other things:
>
> "DAO 3.6 was the final version developed by Microsoft. Microsoft
> says that DAO will not be available in its future 64-bit operating
> systems."
>
> Worth some attention?

Are falsehoods worth more attention than it takes to demonstrate
that they are false?

It's patently untrue and was falsified by the release of Access 2007
which implemented a new version of DAO (i.e., beyond 3.6). The
version and filenaming changed because it's part of the new ACE
rather than part of Jet (which is frozen at version 4 and will not
see further development).

The 64-bit issue was falsified by the release of Access 2010 -- the
64-bit version of DAO is shipped with the 64-bit version of the ACE
that is included with the 64-bit version of Access.

Don't believe what you read on Wikipedia. Don't believe what you
read on MS's own website, much of which has not been updated to
reflect the many zigs and zags of MS's development strategies.

Please let us know what Wikipedia article that is, so it can be
corrected.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
From: Sven Pran on 15 Jul 2010 19:33
"David W. Fenton" wrote
> "Sven Pran" wrote>
>> I am using ADO and didn't know about DAO at all, so I used Google
>> to find some information. What I found on Wikipedia was among
>> other things:
>>
>> "DAO 3.6 was the final version developed by Microsoft. Microsoft
>> says that DAO will not be available in its future 64-bit operating
>> systems."
>>
>> Worth some attention?
>
> Are falsehoods worth more attention than it takes to demonstrate
> that they are false?
>
> It's patently untrue and was falsified by the release of Access 2007
> which implemented a new version of DAO (i.e., beyond 3.6). The
> version and filenaming changed because it's part of the new ACE
> rather than part of Jet (which is frozen at version 4 and will not
> see further development).
>
> The 64-bit issue was falsified by the release of Access 2010 -- the
> 64-bit version of DAO is shipped with the 64-bit version of the ACE
> that is included with the 64-bit version of Access.
>
> Don't believe what you read on Wikipedia. Don't believe what you
> read on MS's own website, much of which has not been updated to
> reflect the many zigs and zags of MS's development strategies.
>
> Please let us know what Wikipedia article that is, so it can be
> corrected.

http://en.wikipedia.org/wiki/Data_Access_Objects

I only referred what I found. To me DAO was of little interest as I use ADO
for communicating with my Access databases and Excel workbooks from my
applications developed in Delphi (at the time I use version 2007).

ADO seems to work fine for me and I hadn't even heard about DAO until I read
about it here, so I just tried to find out what this is all about.

I cannot say that I am much wiser..

regards Sven

From: Tony Toews on 16 Jul 2010 01:03
On Wed, 14 Jul 2010 17:56:49 -0700 (PDT), rkc <rkc(a)rkcny.com> wrote:

>How readable your code is depends entirely on your skills.
>
>Both ADODB and DAO are made up of a conglomeration of objects
>and collections of objects that you have to wade through in order
>to do much of anything.

90% of what I do in DAO is a recordset loop reading a record and dong
something that I can't do in a query. Copy and paste is my friend.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
From: Tony Toews on 16 Jul 2010 01:04
On Wed, 14 Jul 2010 01:14:11 -0700 (PDT), klar <klarbuf(a)gmail.com>
wrote:

>I am using Access2003 and the database will be used locally, not on a
>client-server environment. I will be mainly using ADO/DAO for queries.
>My preferred choice is the one with more readable code. Can the
>experts here advise me ADO or DAO?

I think DAO typically takes one or two less lines of code because you
don't have to create the new ADO object. Or something like that. I
misremember the details now.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: A Totals query problem
Next: Help with table design