Re: Any REAL reason to use ADO vs. DAO?
- From: "Jeff Johnson" <i.get@xxxxxxxxxxx>
- Date: Tue, 1 May 2007 13:32:16 -0400
"Karl E. Peterson" <karl@xxxxxxxx> wrote in message
news:eDgLMMBjHHA.4552@xxxxxxxxxxxxxxxxxxxxxxx
The question should be the other way around, and no there is no reason
to use DAO over ADO,
UNLESS YOU'RE USING .MDBs
UNLESS THE .MDBs ARE ON A WEB SERVER, AND YOU'RE USING VBSCRIPT
IN WHICH CASE YOU ARE INSANE!
For using an MDB rather than SQL Server, or for using ADO? I find MDBs
nice to work with, in most circumstances, because they mesh so darned well
with FrontPage (damning with feint praise, I know). Plus, I can use VBA
inside the MDB for housekeeping, use the same database on both client and
server, yadda yadda yadda...
Oh, I may have read that differently. I'm talking about accessing .MDBs on a
Web server directly from a client, not from ASP code on the server itself.
.
- Follow-Ups:
- Re: Any REAL reason to use ADO vs. DAO?
- From: Karl E. Peterson
- Re: Any REAL reason to use ADO vs. DAO?
- From: Schmidt
- Re: Any REAL reason to use ADO vs. DAO?
- References:
- Re: Any REAL reason to use ADO vs. DAO?
- From: Karl E. Peterson
- Re: Any REAL reason to use ADO vs. DAO?
- From: Jeff Johnson
- Re: Any REAL reason to use ADO vs. DAO?
- From: Karl E. Peterson
- Re: Any REAL reason to use ADO vs. DAO?
- Prev by Date: Re: Need a suggestion for a clickable image (VB6 W2K)
- Next by Date: Re: Notating out old code in Access Database
- Previous by thread: Re: Any REAL reason to use ADO vs. DAO?
- Next by thread: Re: Any REAL reason to use ADO vs. DAO?
- Index(es):
Relevant Pages
|
Loading