I don't know and i want to know the differ of it.
Where can i find that mean??
I'm using Access2000 to connect data with form and i dont know which one is best ?
Thanks first.


To Supremacy

Dear ToSupremacy

Another forum member may be able to give a succinct answer to this question but I think it is too big a question for a forum - books have been written on this subject!

With regard to the merits of ADO and DAO, one reason the answer is not simple is that the answer begins with "it depends...".

One (of many) books that could help you answer this question for your particular needs is "Beginning Access 2003 VBA" (wrox).

R

A good resource to begin exploring is Microsoft's Data Access and Storage Developer Center. All the components you mention are COM libraries developed by MS as part of its Universal Data Access Strategy. ADO.NET represents MS's move away from COM toward a data access technology based on .NET Framework libraries. A look at MS's Data Access Technology Road Map will gives you some good info about where microsoft is going with its data access technologies. You can find it at:

http://msdn.microsoft.com/data/defau...dacroadmap.asp

Technically, DAO is a deprecated (obsolete) data access component library, and will not be included in MS's 64-bit version of Windows when it comes out. Nevertheless, it is optimized for accessing Jet databases, and you will still find plenty of Access developers who recommend its use over ADO when accessing Jet databases. The Jet database engine, however, has also been deprecated, but the jury remains out on the future of Access, and what future versions may use as a data store (probably some incarnation of SQL Server (like MSDE) accessed via ADO.NET).

Also, you can download and install the MDAC (Microsoft Data Access Components) SDK (Software Developer's Kit). The current version is 2.8. The MDAC SDK contains language references and sample code for implementing the COM data access component libraries. The DAO language reference is no longer included, but you can find it in the MSDN library at:

http://msdn.microsoft.com/library/de.../D2/S5A25F.asp

To download and install MDAC 2.8 SDK, go to:

http://www.microsoft.com/downloads/d...DisplayLang=en

For the ADO.NET language reference (which requires the .NET Framework), you will need the .NET Framework SDK 1.1, found at:

http://www.microsoft.com/downloads/d...displaylang=en

HTH,

Bob





http://www.microsoft.com/downloads/d...displaylang=en

You might also find the following helpful. I posted it a while back:

http://p2p.wrox.com/topic.asp?TOPIC_...ms=DAO,vs.,ADO

Pardon me for jumping in with a related question...... We recently implemented a database at work for our workgroup to use (10 people). Our IT department is planning on up-sizing to SQLServer for to meet federal security regulations which go into effect this April. There are places I used DAO to accomplish a few things Access would not allow directly. The little I've read about DAO vs. ADO indicates that ADO can connect to SQL Server but DAO is only for Jet??? And it appears they do not peacefully co-exist well....... So, does the DAO have to be converted to ADO? (I have referred to DAO explicitly).

Thanks,
Loralee

Both DAO and ADO can connect to SQL Server. A DAO connection uses SQL Server's ODBC Driver, while an ADO connection uses SQL Server's OLE DB provider. However, DAO was designed for Jet.

So which do you use to connect to SQL Server?. A general rule of thumb is that when you are working with a database server, whatever it may be, that has both a proprietary ODBC driver and OLE DB provider, you will always get better performance using the OLE DB provider. If you have these two choices, ODBC will always be the poor one. OLE DB is simply a newer and better technology. Plus, migrating form DAO to ADO is really pretty simple, the objects models are generally pretty similar.

HTH,

Bob