Re: adp vs mdb
- From: "'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 23 May 2007 21:25:43 -0700
Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
"Tom Wickerath MDB" <tom_wickerath@xxxxxxxxxxx> wrote in message
news:OunrnlbnHHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
this just flat out ins't true
Access Linked Tables to ODBC = mixing ODBC and OLEDB?
how is MDB linked tables LESS LAYERS than just OLEDB?
isn't ONE LAYER less layers than TWO LAYERS
"Robert Morley" <rmorley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Oa6TmFCmHHA.596@xxxxxxxxxxxxxxxxxxxxxxx
Tne .NET framework is simply not relevant to Access development. The
only options for Access development are MDB and ADP, and Microsoft
has been recommending MDB over ADP for a couple of years now.
I think his point was that you might want to consider .NET as the front
end instead of Access, especially if you're doing Web/Intranet
development. I don't find .NET useful for much, personally, but it has
its advantages in some respects, so others may find it more useful for
whatever they're doing.
The reason MS gives in their documentation is that ADPs have as many
or more layers between your front end and the database as MDBs do,
and those layers are no better at the job than Jet.
I've never seen a strong proof of this. Can you point me to something?
I'm not necessarily disagreeing, but I'd be curious to see more in-depth
analyses than I've seen out of MS to-date.
In the context of Access development, Microsoft has determined that
MDBs with ODBC perform better than ADPs, and they've changed their
recommendations to Access developers developers working with SQL
Server accordingly.
Don't forget, MS has a vested interest in this. They also claimed that
VB.NET was significantly faster than VB6 was, and it was true in a few
highly limited cases. But for most real-world tests, VB.NET proved to be
slower...sometimes quite significantly. MS has a "latest and greatest"
approach to things that doesn't always jive with the real world, so it's
not a good idea to simply take their word for it. Often, they're right,
but often they're trying to get you to buy their newest product, and
skewing things in that product's favour.
MS itself is now saying that MDBs are
better than ADPs. Given that this is a 180 degree reversal of their
position on the subject, it seems like a pretty good justification
for going with MDBs instead of ADPs
Actually, if anything, that makes me highly suspicious. While
highlighting the "latest and greatest" approach I mentioned before, the
fact that they would universally encourage everybody towards ADPs, then
unequivocally urge them back towards MDBs gives me serious cause to
distrust their statements. I'm not particularly anti-MS, but lately, it
seems that a reversal of position is common for them, and that's not a
good sign.
Rob
.
- References:
- adp vs mdb
- From: BillE
- Re: adp vs mdb
- From: Sylvain Lafontaine
- Re: adp vs mdb
- From: David W. Fenton
- Re: adp vs mdb
- From: Robert Morley
- Re: adp vs mdb
- From: Tom Wickerath MDB
- adp vs mdb
- Prev by Date: Re: adp vs mdb
- Next by Date: Re: adp vs mdb
- Previous by thread: Re: adp vs mdb
- Next by thread: Re: adp vs mdb
- Index(es):
Relevant Pages
|