Re: DAO vs ADO


I disagree with your analysis of DAO vs ADO.

for starters, MDB is a DEAD FORMAT, anyone that uses it anywhere should
be fired and then spit upon.

and try comparing that to an Access Data Project and ADO

we don't have DBAs; you _ARE_ the DBA

if you don't know enoug about SQL to build a database from scratch then
you shouldn't be a programmer

-Aaron

Michel wrote:
wait !!! before i start a flame war :-)

when i reread the below line i thought it might be interpreted the wrong way

however this requires
skills that most VB proggers do not posess

With this line i actually mean that not all VB ( or C# , J# etc etc )
coders have enough knowledge of SQL server to perform these tasks . That`s
why we have Dba`s .

regards

Michel







"Michel Posseth [MCP]" wrote:

DAO is specially optimized for ACCESS ( Native )

ADO is just a uniform way of acessing datasources through a provider
so they can`t be compared in this way

And for .Net they are both Obsolete so irrelevant ( DAO was / is even
obsolete for VB6 )

As we are here in microsoft.public.dotnet , we do it now the recomended way
import all data to a SQL 2005 MDF with SMS , now create T-SQL query`s , and
now analyze this query in the database engine tuning advisor , apply al
recomendations , now run this query from your VB.Net application ( with the
sql native client provider )

what do you see now ?

You wil probably see that the access database performance is blown away and
we ar not even at max , cause we could also create SP`s , indexed views ,
create functions etc etc to do some final tuning , however this requires
skills that most VB proggers do not posess

regards

Michel




"Alan Welsford" wrote:

ADO Code 66 Seconds

Set dcndb = New ADODB.Connection
dcndb.Provider = "Microsoft.Jet.OLEDB.4.0"
dcndb.ConnectionString = "Data Source=" + dtbs$
dcndb.Open
Set rsUsers = New ADODB.Recordset
rsUsers.Open Sql$, dcndb, adOpenForwardOnly, adLockReadOnly

DAO Code 20 Seconds

Set rDb = DBEngine.Workspaces(0).OpenDatabase(dtbs$)
Set rsUsers = rDb.OpenRecordset(Sql$)



*** Sent via Developersdex http://www.developersdex.com ***


.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... code and connect to a single SQL Server database, ... If you run into issues with the ADP solution, ... First they recommended DAO, then ADO, and now DAO again. ...
    (microsoft.public.sqlserver.connect)
  • Re: supports(adIndex) = False
    ... While I am sure that Denise can appreciate your passion about using DAO (yes ... is trying to achieve using ADO really should be quite simple and there's no ... It is not Jet centric. ... you can do most stuff in SQL Server using DAO pass through queries ...
    (microsoft.public.access.modulesdaovba)
  • Re: supports(adIndex) = False
    ... While I am sure that Denise can appreciate your passion about using DAO (yes ... is trying to achieve using ADO really should be quite simple and there's no ... It is not Jet centric. ... you can do most stuff in SQL Server using DAO pass through queries ...
    (microsoft.public.access.modulesdaovba)
  • Re: Allen Brownes ErrorLog Function + SQL Server problem
    ... I have to take some more time to study both ADO and DAO some more to fully ... So when I use the AttachDSNLessTable code to connect my tables to the SQL ... Debug.Print strCallingProc & " called error 0." ...
    (microsoft.public.access.formscoding)
  • Re: DAO vs ADO
    ... Set dcndb = New ADODB.Connection ... Set rsUsers = New ADODB.Recordset ... DAO Code 20 Seconds ... the 66 seconds for ADO does seem an inordinate time as does 20 seconds ...
    (microsoft.public.dotnet.languages.vb)