Re: VBA CODE - ADODB
- From: "MikeD" <nobody@xxxxxxxxxxx>
- Date: Fri, 30 Dec 2005 08:56:24 -0500
"David J Mark" <nntp45534-22@xxxxxxxxxxxx> wrote in message
news:y27tf.91967$lh.4359@xxxxxxxxxxxxxxxxxxxxxxxxx
>
> 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?
--
Mike
Microsoft MVP Visual Basic
.
- References:
- Re: VBA CODE - ADODB
- From: MikeD
- Re: VBA CODE - ADODB
- From: David J Mark
- Re: VBA CODE - ADODB
- Prev by Date: Re: Default Error
- Next by Date: Subclassing VBA/VB6/.Net
- Previous by thread: Re: VBA CODE - ADODB
- Next by thread: Re: VBA CODE - ADODB
- Index(es):
Relevant Pages
|
Loading