Re: Any REAL reason to use ADO vs. DAO?
- From: "Jim Carlock" <anonymous@localhost>
- Date: Tue, 1 May 2007 09:47:09 -0400
"Karl E. Peterson" <karl@xxxxxxxx> wrote...
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
"Jeff Johnson" <i.get@xxxxxxxxxxx> wrote...
: IN WHICH CASE YOU ARE INSANE!
I'm interested. What's wrong with an .mdb on a webserver using DAO?
You mean the 250 connection limit? Is that the only thing wrong?
Or you mean that an .mdb needs to run on a Windows server? Okay,
I'll go along with that one.
Hmmm... You guys have got me interested. I'm interested in all replies.
--
Jim Carlock
Post replies the group.
.
- Follow-Ups:
- Re: Any REAL reason to use ADO vs. DAO?
- From: David Kerber
- Re: Any REAL reason to use ADO vs. DAO?
- From: Jeff Johnson
- 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?
- Prev by Date: Creating a variable with NaN
- Next by Date: Re: ADO update and tables with more than 127 fileds
- 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
|