Re: Table adapter ???
- From: "Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom>
- Date: Wed, 27 Jun 2007 19:46:42 +0100
"Marty" <radiolandog@xxxxxxxxxxxxx> wrote in message
news:eoaVUXNuHHA.484@xxxxxxxxxxxxxxxxxxxxxxx
What distingushes "classic ADO" from ADO.net?
Classic ADO is independent of .NET technology, it does not need it.
ADO (and ADOX, ADOMD) was a lightweight COM layer built on top of OLE DB.
So all it requires is COM support from Windows, nothing else.
With the Connection, Recordset and Command object, it made access to data
easy.
ADO and OLE DB updates came in downloads of the MDAC pack (Microsoft Data
Access Components).
MDAC came with Native providers (OLE DB speak for "drivers") for OLE DB, in
particular SQL Server, Oracle & Access (later deprecated).
It also came with a OLE DB provider for ODBC (also deprecated) which meant
that if all you had was a ODBC driver for some unusual database, you could
use this "piggyback" provider to get to your data.
A full history of MDAC is here
http://en.wikipedia.org/wiki/Microsoft_Data_Access_Components
ADO history is also here
http://msdn2.microsoft.com/en-us/library/ms676506.aspx
ADO.NET is a component of .NET, part of the Microsoft .NET Framework
In contrast to ADO, it has no Recordset object but a DataAdapter and
DataReader objects
I dont beleive you can use ADO.NET outside of a .NET.
See here
http://msdn2.microsoft.com/en-us/library/e80y5yhx.aspx
http://en.wikipedia.org/wiki/Ado.net
Stephen Howe
.
- References:
- Re: Table adapter ???
- From: Marty
- Re: Table adapter ???
- Prev by Date: Re: ADO recordset doesn't see DB changes
- Next by Date: Does anyone know any commercial C++/CLI GUI library with source code?
- Previous by thread: Re: Table adapter ???
- Next by thread: Re: ADO recordset doesn't see DB changes
- Index(es):
Relevant Pages
|
|
