Re: Fastest record create method with JET 4.0


"Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom> wrote in message
news:uWQiNCz1GHA.1040@xxxxxxxxxxxxxxxxxxxxxxx
As someone else pointed out, DAO code may be written shoddy and still
do the job. Even with lazy code, DAO ought to be faster at inserting
records into an Access database than ADO, even though Microsoft says
otherwise.

Where do they say that?
I believe Microsoft do acknowledge DAO is faster than ADO for Access
databases
See http://support.microsoft.com/kb/225048/
where you can read what DAO and ADO philosophy.

But frequently programmers use ADO badly so the performance difference
may
not be that apprecaibly different.

Stephen Howe


Just to be boorish for a moment.

MS has switched its "pronouncements" several times concerning DAO. When ADO
first appeared, ADO was touted as being the only way to go, and that all
subsquent development of DAO was going to be discontinued. DAO 3.6 slipped
in rather quietly.

While I am not sure MS themselves ever stated "ADO is faster". Many authors
and insiders certainly did. I believe most of the time it was just an extra
adjective tacked on without too much thought (and certainly without
testing). After all once you have proclaimed something as prettier, slicker,
cleaner, simpler, neater, ... What is more natural that to proclaim it
'faster'?

The waters also became cloudier at this time, because OLE DB was also
introduced. Many comparisons were made at the time comparing DAO with ADO,
with the unfortunate underlying, but understated, actual comparison of ODBC
with OLE DB. "DAO" always came out the loser. (With one exception DB2)

You make a good point, that ultimately it always comes down to how you are
using the tool. A common discovery when visiting teams using ADO and chewing
away on some 'performance' problem, is to examine the connection string and
learn that they are using ODBC or an outdated provider. <g>

-ralph








.

Relevant Pages

  • ADO connection Open failure
    ... At some point in the code I'm using ADO to export an Access dataset. ... Access database on the shared drive; ... The Excel file is using the following references: ... Microsoft Office 11.0 Object Library ...
    (microsoft.public.excel.programming)
  • Re: How to enforce subtypes/supertypes in Access 2000?
    ... why do you prefer DAO over ADO? ... because Microsoft does not plan to provide any future enhancements for the ... Private Sub SetContactType() ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Import Text with existing schema.ini file utility
    ... but the first bit of schema.ini documentation for Jet that I ... >the Microsoft Jet Database engine and I would need to upgrade to the latest. ... >Thank you for explaining well the issues involving ADO and DAO. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Import Text with existing schema.ini file utility
    ... the Microsoft Jet Database engine and I would need to upgrade to the latest. ... Thank you for explaining well the issues involving ADO and DAO. ...
    (microsoft.public.access.modulesdaovba)
  • Re: CHANGING from DAO to RDO
    ... > For a long while, Microsoft was heavily promoting ADO, but in recent times, ... > I don't know _where_ you got the idea that ADO and RDO were the only methods ... > DAO and, for them too, DAO was simpler and easier. ... > found about performance and avoiding corruption in the Access - Jet ...
    (microsoft.public.access.modulesdaovba)