Re: Speed of working on Access tables
- From: Cindy M. <C.Meister-C@xxxxxxxxxx>
- Date: Fri, 08 Sep 2006 11:54:53 +0200
Hi =?Utf-8?B?cGF1bGFkYW1zNzc3?=,
You'd probably get a better discussion in an Access-dedicated newsgroup, but...
Generally, working with DAO - the Jet Engine's "native language" - will be
faster than any other method. ODBC and OLE DB providers both, if I remember
correctly, interface internally with DAO, adding an extra "layer".
FWIW, it might be faster to run INSERTINTO and UPDATE queries than opening
tables. Might be worth a test.
I found the subject a tough one to adequately summarise.
Basically, I am writing a C++ application that needs to write content to an
Access database. The database already exists, so I don't need to create the
database or tables at runtime.
All I need to do is open tables, create records, populate fields and save
the records. I don't query, delete, restructure or even read existing
records.
Currently, I am using ADO to access the Jet 4.0 engine, but I cannot believe
how slow this is compared to other databases I work with.
My question is therefore in two parts.
What methods can I use to do the work on the Access database that I have
described above?
What methods are the fastest?
I have read that ODBC is faster than ADO, but don't know anything about
ODBC. I have also gained the impression that it is a "dated technology" -
possibly even deprecated.
Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org
This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail :-)
.
- Prev by Date: Re: Building Word documents using C#
- Next by Date: Adding a watermark to a document
- Previous by thread: Re: Building Word documents using C#
- Next by thread: Re: Speed of working on Access tables
- Index(es):
Relevant Pages
|
|
