Re: ADO from DAO

We have seen from past experience that ADO can be slower than DAO in many
respects. ADO is an "OSFA" interface while DAO is a JET/Access database
specific data interface. However, at this time you should consider moving
your programs and skills to .NET instead of to ADO classic. Will .NET be any
faster? Possibly not--but in my experience, most performance issues are
caused by design issues--not which data access interface you choose.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.

"Lhunt" <Lhunt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8163A388-62DE-4510-AADD-3C5E4EF4FA4F@xxxxxxxxxxxxxxxx
>I have done the preliminary conversion from DAO to ADO on MSACCESS (350
>megs
> in 5 tables) and it is much slower in multi-user (3 workstations) on a
> Wndows
> 2000 server.
>
> I tried adUseClient and it was worse
>
> QUESTION: There are so many variables to adjust I am sure there is an
> Optimized setup. Which properties should be changed to optimize or even
> improve the speed.
>
> Set DB = New ADODB.Connection
> DB.Provider = "Microsoft.JET.OLEDB.4.0"
> DB.Properties("Data Source") = DbLoc$ & "\" & DataBaseName$
> '=====================================
> '== Lock Rows with Locking Mode = 1
> '=====================================
> DB.Properties("Jet OLEDB:Database Locking Mode") = 1
> ' == DB.Properties("RecordSource") = adCmdTable
> DB.CursorLocation = adUseServer
> DB.Open
>
> Set PatDATA = New ADODB.Recordset
> PatDATA.Open "Visits", DB, adOpenstatic, adLockOptimistic
>
> This has 36000 rows.
>
> patdata.findfirst ("[PT_ID] = " & pt_NUM
>
> This will take 30 - 40 seconds to pull up.
>
> Similar code in DAO is up in seconds?
>
>


.

Relevant Pages

  • Re: ADO vs DAO
    ... DAO is faster than ADO just ... as simple file IO is faster than DAO. ... "OSFA" interface designed to permit a common programming ... DAO is that it does not scaled due to its dependency on JET and its overall ...
    (microsoft.public.vb.database.ado)
  • Re: A common problem : ADO vs DAO slower
    ... Dave Patrick ....Please no email replies - reply in newsgroup. ... | we have migrated our application that uses an MS Access database from DAO ... | Now we encounter the most common problem: ADO is slower than DAO. ...
    (microsoft.public.data.ado)
  • A common problem : ADO vs DAO slower
    ... we have migrated our application that uses an MS Access database from DAO to ... Now we encounter the most common problem: ADO is slower than DAO. ...
    (microsoft.public.data.ado)
  • Re: How to enforce subtypes/supertypes in Access 2000?
    ... DAO is the native object model for Jet databases and, as such, is the ... ever need ADO. ... Private Sub SetContactType() ...
    (microsoft.public.access.tablesdbdesign)
  • Re: ADODB reference?
    ... will play around with DAO in A2007 after I finish my current test ... I had one other question about ADO connection string syntax in case ... to a variety of data sources but not designed specifically for Access. ...
    (microsoft.public.access.modulesdaovba)