Re: Fastest record create method with JET 4.0


pauladams777 wrote:
Thanks Desertphile,

I remembered Microsoft talking about the ADO / DAO comparison at a
developers conference some time back and running a demo program - I think
that could be the one they showed.

I will have a look and see how much it gets me "in"...

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.

If it is much data, you could start the insert process by first
expanding the Access database by many "pages" based on the Paradox
record count of what is anticipated to be added to the Access database:
that way the database only expands once instead of several times as
data is added.

The following is from Microsoft's Knowledge Base: "DAO provides a
consistent programming model for situations where some of the data
access services must be provided using Microsoft Jet." Since your
write-to database is a JET Access .MDB file, DAO is the recomended data
transport layer.

Microsoft says that DAO is slower than ADO and RDO: merely inserting
records into a .MDB file, though, appears by my tests to be faster with
DAO by around 30%. Many of the MS Knowledgebase articles state that one
should use ADO instead of DAO, since DAO has a larger "overhead" and
has fewer connectivity issues (present and future). If you expect no
future need to modify your Paradox-to-Access translation program, such
as sending the translation to an SQL server on a LAN or over the
Internet, then DAO will be just fine; otherwise you might want to stay
with ADO.

OLE DB is also an option, as is RDO. Dang, too may options to choose
from! :-)

.

Relevant Pages

  • 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)
  • 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. ... 70 MB is not an exceptionally large Access database -- you have 1930 MB more ...
    (microsoft.public.access.modulesdaovba)