Re: Why not use DAO?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Michael,

I ignored most of your message because you are not providing any real
infromation. Simply saying "don't use this because the powers that be say
it's obsolete" doesn't quite cut it.

What is not in doubt is that DAO has historically been the fastest interface
for working with JET databases. Saying otherwise is just not true.

Also, speaking of apples and pears, why are you talking about TableAdapters
and recordsets, when we are talikng about data access and not data
storage/manipulation?

Having said all of this, I personally use the OLE DB Provider for JET when
using Access databases because I prefer the availability of the provider.
But, let's be clear...whatever provider/driver you use, the data can be
loaded up into whatever container you wish.

"Michel Posseth [MCP]" <MSDN@xxxxxxxxxxx> wrote in message
news:e99irFnJHHA.1468@xxxxxxxxxxxxxxxxxxxxxxx
Well especially for Stephany ..

Let me be the one that tells you "don`t use DAO" and with that i mean stay
away of it there is only one exception in my opinion when you should
still use it
"You are a VB6 programmer , and need to maintain a prog written with DAO "

In VB.Net ( all versions ) it is a definite no go
Why ?? well because it is absolutely undeniable obsolete , i would also
not recomend classic ADO cause it is obsolete because we have ADO.Net
DAO is in most situations faster on a Access database ,,, there is no
discussion about that ( DAO was also faster as classic ADO )

However i would recomend you to use a mdf in your projects , this will
blast away the perfomance of Access and is the bether way as using
obsolete products in your newly to deploy application.

By the way a standard ADO recordset with a firehose cursor is also much
faster as a typical ADO.Net table adapter aproach however if you use a
datareader they perform equall ADO.Net might even be faster on SQL server
cause it uses a optimized driver so don`t compare pears with apples :-)


regards

Michel Posseth [MCP]





"Cor Ligthert [MVP]" <notmyfirstname@xxxxxxxxx> schreef in bericht
news:euLl3dYJHHA.4960@xxxxxxxxxxxxxxxxxxxxxxx
TC,

I have an opposite opinion as Stephany, I surely would not go the road
from DAO. Even moreover, I would not go any direction using the Jet
Engine for new applications. We don't know how long it will be on newer
OS. Therefore just go to SQLExpress as is often told in these newsgroups
is in my idea a better approach.

I am with Stephany curious about your code, although it is known that DAO
is slightly quicker than all other that is made after it.

Cor


"TC" <golemdanube@xxxxxxxxx> schreef in bericht
news:1166759603.848542.136520@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I love ADO.NET, but I find OLEDB to be unacceptably slow. The last time
I tried to use a Jet database for local data storage, I gave up and
wrote my data to a binary flat file instead. This time, I really need
to use a relational database, so I've been making the best of OLEDB and
cursing its performance.

A few days ago, however, I tried an experiment and wrote a
DAODataAdapter class, which implements DataAdapter using DAO. For
updates to an .mdb file, it is 4x faster than OLEDbDataAdapter!

So now I have a dilemma. Should I use DAO in my shiny new NET
application? I know DAO is deprecated; I know COM objects have memory
issues and use a different architecture than NET objects; I know this,
but I'm not going to ignore a 4x difference in performance.

My plan, therefore, is to use DAO and damn the consequences. I'm
posting here just to find out what other experienced NET developers
think about this. Certainly, I'm not the first person to go down this
road, and I'm curious what choices others have made.


-TC







.

Relevant Pages

  • Re: Missing DAO licence on target PC
    ... compare SQL + ADO to JET + DAO ... but JET is obsolete; and who wants to use an obsolete DAL just because ... DAO and JET have both been obsoleted for a decade. ... DAO doesn't fit into the 'worlds most popular database' and it hasn't ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Missing DAO licence on target PC
    ... you on, that does, in fact, mean he's got a JET database. ... So the fact is that the OP has a JET database and the fact is the DAO is ... No one is disputing that DAO is obsolete. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Missing DAO licence on target PC
    ... there is no point to using DAO and Jet. ... you on, that does, in fact, mean he's got a JET database. ... No one is disputing that DAO is obsolete. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Missing DAO licence on target PC
    ... May I ask you if you are already obsolete or can you still go on? ... compare SQL + ADO to JET + DAO ... DAO and JET have both been obsoleted for a decade. ... DAO doesn't fit into the 'worlds most popular database' and it hasn't ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Build a query "on the fly"
    ... ADO classic is not obsolete. ... ACEDAO has ... classic can use the new OLE DB provider but ACEDAO cannot. ...
    (microsoft.public.access.forms)