Re: Complete Beginner's question
- From: "Scot T Brennecke" <ScotB@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 10 Mar 2007 18:51:41 -0600
DAO is primarily intended for the older versions of Access -- consider it DOA (Dead On Arrival) now.
MFC classes for it survive because they still work, and some people would get upset if they were
removed.
Microsoft OLE DB:
http://msdn2.microsoft.com/en-us/library/ms722784.aspx
Microsoft Open Database Connectivity (ODBC) Start Page (Microsoft Open Database Connectivity
(ODBC)):
http://msdn.microsoft.com/library/en-us/odbc/htm/dasdkodbcoverview.asp?frame=true
Microsoft Active X Data Objects (ADO):
http://msdn.microsoft.com/library/en-us/ado270/htm/dasdkadooverview.asp?frame=true
ADO.NET:
http://msdn2.microsoft.com/en-us/library/e80y5yhx.aspx
You will need to choose from these based on a number of factors:
* Which programming language you're using (C++ and MFC?).
* Whether you are creating a managed (.NET) application or not.
* Whether you need lightweight code or easier-to-write code.
* Whether or not your database of choice has a driver or provider for the desired interface.
* Your preference.
"Jacky" <jl@xxxxxxxxxx> wrote in message news:uuAOwjiYHHA.992@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I wonder what are the differences between DAO, OLE DB and ODBC?
and the .NET versions of these?
How come MFC doesn't support OLE DB? But also why do MS keep DAO if the technology is obsolete?
What are ADO and ADO.NET? seems a lot of technologies that look so daunting!!
Thanks
.
- References:
- Complete Beginner's question
- From: Jacky
- Complete Beginner's question
- Prev by Date: Re: MS ODBC and Null terminated strings
- Next by Date: Re: 32 bit ODBC in Win XP x64?
- Previous by thread: Complete Beginner's question
- Next by thread: x64 ODBC CSV Drivers
- Index(es):
Relevant Pages
|
