ADO

Do front end apps have to use ADO to connect to SQL Server ? If not, what
else can they use ? Just trying to get familiar with the terminology from a
client portion of the code that uses SQL ServerHassan wrote:
> Do front end apps have to use ADO to connect to SQL Server ? If not,
> what else can they use ? Just trying to get familiar with the
> terminology from a client portion of the code that uses SQL Server
ADO.Net, ADO, ODBC, RDO, dbLib, and so on.
If you're writing an application in .Net, use the native SQL Server
driver. ADO and ODBC are good options as well.
David Gugick
Imceda Software
www.imceda.com|||So is ADO just another data access component then ? And is it bundled with
MDAC ?
I thought ADO is a layer over ODBC or OLE DB and uses one of those
components , but did not know it was another access component .
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:uU65JiNEFHA.548@.TK2MSFTNGP14.phx.gbl...
> Hassan wrote:
> > Do front end apps have to use ADO to connect to SQL Server ? If not,
> > what else can they use ? Just trying to get familiar with the
> > terminology from a client portion of the code that uses SQL Server
> ADO.Net, ADO, ODBC, RDO, dbLib, and so on.
> If you're writing an application in .Net, use the native SQL Server
> driver. ADO and ODBC are good options as well.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Hi
ADO is the programming interface to ODBC, OLE DB etc. It is a layer above
the drivers, your assumption is correct.
It relies on the other components in the MDAC stack, plus data
driver/providers supplied by Microsoft and other vendors.
DAO was used mostly for Microsoft Access (and later SQL Server) and was the
first non direct API interface, then came RDO, then ADO and now ADO.NET.
All of the above 4 programming interfaces can communicate with ODBC and OLE
DB providers.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:e397LgTEFHA.3120@.TK2MSFTNGP12.phx.gbl...
> So is ADO just another data access component then ? And is it bundled with
> MDAC ?
> I thought ADO is a layer over ODBC or OLE DB and uses one of those
> components , but did not know it was another access component .
> "David Gugick" <davidg-nospam@.imceda.com> wrote in message
> news:uU65JiNEFHA.548@.TK2MSFTNGP14.phx.gbl...
> > Hassan wrote:
> > > Do front end apps have to use ADO to connect to SQL Server ? If not,
> > > what else can they use ? Just trying to get familiar with the
> > > terminology from a client portion of the code that uses SQL Server
> >
> > ADO.Net, ADO, ODBC, RDO, dbLib, and so on.
> >
> > If you're writing an application in .Net, use the native SQL Server
> > driver. ADO and ODBC are good options as well.
> >
> >
> > --
> > David Gugick
> > Imceda Software
> > www.imceda.com
> >
>|||Could you in lay man terms explain why one would use ADO instead of OLEDB
directly ? And can we use ADO in ASP.net as well ?
A simple example on using ADO vs using OLEDB would help ?
Thanks
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uwFZ8lTEFHA.1348@.TK2MSFTNGP14.phx.gbl...
> Hi
> ADO is the programming interface to ODBC, OLE DB etc. It is a layer above
> the drivers, your assumption is correct.
> It relies on the other components in the MDAC stack, plus data
> driver/providers supplied by Microsoft and other vendors.
> DAO was used mostly for Microsoft Access (and later SQL Server) and was
the
> first non direct API interface, then came RDO, then ADO and now ADO.NET.
> All of the above 4 programming interfaces can communicate with ODBC and
OLE
> DB providers.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:e397LgTEFHA.3120@.TK2MSFTNGP12.phx.gbl...
> > So is ADO just another data access component then ? And is it bundled
with
> > MDAC ?
> >
> > I thought ADO is a layer over ODBC or OLE DB and uses one of those
> > components , but did not know it was another access component .
> >
> > "David Gugick" <davidg-nospam@.imceda.com> wrote in message
> > news:uU65JiNEFHA.548@.TK2MSFTNGP14.phx.gbl...
> > > Hassan wrote:
> > > > Do front end apps have to use ADO to connect to SQL Server ? If not,
> > > > what else can they use ? Just trying to get familiar with the
> > > > terminology from a client portion of the code that uses SQL Server
> > >
> > > ADO.Net, ADO, ODBC, RDO, dbLib, and so on.
> > >
> > > If you're writing an application in .Net, use the native SQL Server
> > > driver. ADO and ODBC are good options as well.
> > >
> > >
> > > --
> > > David Gugick
> > > Imceda Software
> > > www.imceda.com
> > >
> >
> >
>|||I don't have a simple example since to me there is nothing simple about
programming at the OLEDB level<g>. ADO sits on top of OLEDB and provides a
much simpler object model to work the data with and allows it to tie
directly into many objects such as data grids, textboxes etc. ASP.NET uses
ADO.net. ADO.net is similar to ADO but more advanced so to speak.
Everything is a collection in ADO.net as compared to some things in ADO that
were not. Its a huge subject and I recommend you have a look here:
http://msdn.microsoft.com/data/Default.aspx
Andrew J. Kelly SQL MVP
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23xgat8VEFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Could you in lay man terms explain why one would use ADO instead of OLEDB
> directly ? And can we use ADO in ASP.net as well ?
> A simple example on using ADO vs using OLEDB would help ?
> Thanks
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uwFZ8lTEFHA.1348@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> ADO is the programming interface to ODBC, OLE DB etc. It is a layer above
>> the drivers, your assumption is correct.
>> It relies on the other components in the MDAC stack, plus data
>> driver/providers supplied by Microsoft and other vendors.
>> DAO was used mostly for Microsoft Access (and later SQL Server) and was
> the
>> first non direct API interface, then came RDO, then ADO and now ADO.NET.
>> All of the above 4 programming interfaces can communicate with ODBC and
> OLE
>> DB providers.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "Hassan" <fatima_ja@.hotmail.com> wrote in message
>> news:e397LgTEFHA.3120@.TK2MSFTNGP12.phx.gbl...
>> > So is ADO just another data access component then ? And is it bundled
> with
>> > MDAC ?
>> >
>> > I thought ADO is a layer over ODBC or OLE DB and uses one of those
>> > components , but did not know it was another access component .
>> >
>> > "David Gugick" <davidg-nospam@.imceda.com> wrote in message
>> > news:uU65JiNEFHA.548@.TK2MSFTNGP14.phx.gbl...
>> > > Hassan wrote:
>> > > > Do front end apps have to use ADO to connect to SQL Server ? If
>> > > > not,
>> > > > what else can they use ? Just trying to get familiar with the
>> > > > terminology from a client portion of the code that uses SQL Server
>> > >
>> > > ADO.Net, ADO, ODBC, RDO, dbLib, and so on.
>> > >
>> > > If you're writing an application in .Net, use the native SQL Server
>> > > driver. ADO and ODBC are good options as well.
>> > >
>> > >
>> > > --
>> > > David Gugick
>> > > Imceda Software
>> > > www.imceda.com
>> > >
>> >
>> >
>>
>|||Hi
OLE DB, you need to usually use C++ as you are calling API's directly.
ADO.NET is the correct way of utilizing data access in .NET, including
ASP.NET.
When doing .NET development, you are not using the best tool for the job if
you are not using the managed .NET data providers, and means ADO.NET.
ADO is ASP.NET, IMHO, is for lazy developers who don't want to change any
code that they used to use in the bad ASP/VB6 days.
Eventually, ADO will no longer be supported, and ADO.NET is the way forward
for Microsoft.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:#xgat8VEFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Could you in lay man terms explain why one would use ADO instead of OLEDB
> directly ? And can we use ADO in ASP.net as well ?
> A simple example on using ADO vs using OLEDB would help ?
> Thanks
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uwFZ8lTEFHA.1348@.TK2MSFTNGP14.phx.gbl...
> > Hi
> >
> > ADO is the programming interface to ODBC, OLE DB etc. It is a layer
above
> > the drivers, your assumption is correct.
> > It relies on the other components in the MDAC stack, plus data
> > driver/providers supplied by Microsoft and other vendors.
> >
> > DAO was used mostly for Microsoft Access (and later SQL Server) and was
> the
> > first non direct API interface, then came RDO, then ADO and now ADO.NET.
> >
> > All of the above 4 programming interfaces can communicate with ODBC and
> OLE
> > DB providers.
> >
> > Regards
> > --
> > Mike Epprecht, Microsoft SQL Server MVP
> > Zurich, Switzerland
> >
> > IM: mike@.epprecht.net
> >
> > MVP Program: http://www.microsoft.com/mvp
> >
> > Blog: http://www.msmvps.com/epprecht/
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:e397LgTEFHA.3120@.TK2MSFTNGP12.phx.gbl...
> > > So is ADO just another data access component then ? And is it bundled
> with
> > > MDAC ?
> > >
> > > I thought ADO is a layer over ODBC or OLE DB and uses one of those
> > > components , but did not know it was another access component .
> > >
> > > "David Gugick" <davidg-nospam@.imceda.com> wrote in message
> > > news:uU65JiNEFHA.548@.TK2MSFTNGP14.phx.gbl...
> > > > Hassan wrote:
> > > > > Do front end apps have to use ADO to connect to SQL Server ? If
not,
> > > > > what else can they use ? Just trying to get familiar with the
> > > > > terminology from a client portion of the code that uses SQL Server
> > > >
> > > > ADO.Net, ADO, ODBC, RDO, dbLib, and so on.
> > > >
> > > > If you're writing an application in .Net, use the native SQL Server
> > > > driver. ADO and ODBC are good options as well.
> > > >
> > > >
> > > > --
> > > > David Gugick
> > > > Imceda Software
> > > > www.imceda.com
> > > >
> > >
> > >
> >
> >
>