Prev: CreateObject Error 91 Object variable or With block variable not set
Next: MSDN98, MSDN Library Visual Studio 6.0a
From: MikeD on 30 Dec 2005 08:56
"David J Mark" <nntp45534-22(a)newsdesk.net> wrote in message
> No. You do not want to use DAO with Access or anything else at this time.
> ADO is the way to go.
A lot of knowledgeable people will disagree with that.
>> DAO. One reason is that you're apparently already somewhat familiar with
>> it. A second reason is there's no advantage that ADO is going to give you
>> for an Access backend database. In fact, DAO is slightly more efficient
>> than ADO with Access databases.
> This is not true. It all depends on the code and queries. Granted that
> most VB/DB code is so God-awful that the database layer doesn't matter.
That's true of *anything*. One can write bad C++ code just as easily as one
can write bad VB code. Sure, if the code and queries are poorly written,
performance is going to suffer. Bad code and queries in a C++ app are also
going to hurt performance.
> If you really want to open recordsets and seek through them, etc. then ADO
> is not going to help.
Aren't you contradicting yourself?
Microsoft MVP Visual Basic