ADO.NET vs ADO

[Kevinp]

Just a silly question probably...

I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using 2008. When I started programming, VB5 was just out and I was using RDO. I loved ADO when it came out and quickly switched all my programs to use it.

I've tried to make the switch to ADO.NET, but just can't seem to figure out what I'm doing most of the time. I'm using it in just a couple of forms where I needed it to work with a DataGridView and to update a few records.

Am I the only stupid one out there that would rather use the old ADO? Is there an easy way to learn ADO.NET?

[a a r o n _ k e m p f]

Re: ADO.NET vs ADO

I prefer the old ADO to anything else out there.

Sorry, but I'll use it for another decade probably.

-Aaron



On Oct 17, 6:35 pm, Kevinp <kev...@nospam. comwrote:

Just a silly question probably...
>
I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using 2008. When I started programming, VB5 was just out and I was using RDO. I loved ADO when it came out and quickly switched all my programs to use it.
>
I've tried to make the switch to ADO.NET, but just can't seem to figure out what I'm doing most of the time. I'm using it in just a couple of forms where I needed it to work with a DataGridView and to update a few records.
>
Am I the only stupid one out there that would rather use the old ADO? Is there an easy way to learn ADO.NET?

[a a r o n _ k e m p f]

Re: ADO.NET vs ADO

Dreamweaver still writes perfectly solid ADO, and Adobe just cancelled
the ASP.net functionality.. so if I had to bet-- I think that classic
ASP / classic ADO is here for the next decade at least.

-Aaron







On Oct 17, 6:35 pm, Kevinp <kev...@nospam. comwrote:

Just a silly question probably...
>
I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using 2008. When I started programming, VB5 was just out and I was using RDO. I loved ADO when it came out and quickly switched all my programs to use it.
>
I've tried to make the switch to ADO.NET, but just can't seem to figure out what I'm doing most of the time. I'm using it in just a couple of forms where I needed it to work with a DataGridView and to update a few records.
>
Am I the only stupid one out there that would rather use the old ADO? Is there an easy way to learn ADO.NET?

[Cor Ligthert[MVP]]

Re: ADO.NET vs ADO

Kevin,

Especially as it is for a couple of forms have then a look at Linq to SQL
probably the most easiest switch from Ado to Ado.Net

You need to set your application to work with Framework 3.5. Don't forget to
use the bindingsource instead of directly the datasource of your controls.

http://msdn.microsoft.com/en-us/library/bb425822.aspx

Cor




Cor

"Kevinp" <kevinp@nospam. comwrote in message
news:4i9if41c7c rojv10pkhmt9v8h p4o2dk1fg@4ax.c om...

Just a silly question probably...
>
I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using
2008. When I started programming, VB5 was just out and I was using RDO. I
loved ADO when it came out and quickly switched all my programs to use it.
>
I've tried to make the switch to ADO.NET, but just can't seem to figure
out what I'm doing most of the time. I'm using it in just a couple of
forms where I needed it to work with a DataGridView and to update a few
records.
>
Am I the only stupid one out there that would rather use the old ADO? Is
there an easy way to learn ADO.NET?

[Michel Posseth [MCP]]

Re: ADO.NET vs ADO


1. See the thread from Mr X "ADODB on dotnet" just a few entrys below in
this group see my links and small example

2. Buy yourself a good ADO.Net Book like on of these

http://astore.amazon.com/vbdotnetcoder-20?%5Fencoding=UTF8&node=9

play a few hours with it and you are good to go i personally learned a
lot from ADO.Net from the "core reference" guides .

Although it is still possible to use classic ADODB in .Net i would sure not
recommend it for new to develop applications, and even bether i would
recomend you to upgrade ADODB code to ADO.Net as it would sure benefit your
application.

When you were already a classic ADO and not a DAO programmer the learning
curve is not so high for ADO.Net , for people who in the VB classic days
only used DAO i would recomend to start with the "step by step" book and
take a few days to play with it .

i wil say again what i posted a few threads below

"the prefered way in .Net languages to access data and data services is
ADO.Net and not ADODB
it is as simple as ADO.Net = .Net and ADODB = legacy So if you program
in .Net wich one should be prefered ?"

And before a new flame war is started here , yes indeed ADODB can be used in
..Net this has everything to do with portability of code and the simple fact
that
ADODB is fully COM compatible so if MS wanted to stop you from using ADODB
they should abandon COM completely wich is not likely to happen for the
following years to come , and No there is nut such a thing as the ADODB
police that would stop you from using it , However i do not believe it is a
smart thing for you , your customers or for the coders that in a later
stage must support your code to do so

regards

Michel



"Kevinp" <kevinp@nospam. comschreef in bericht
news:4i9if41c7c rojv10pkhmt9v8h p4o2dk1fg@4ax.c om...

Just a silly question probably...
>
I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using
2008. When I started programming, VB5 was just out and I was using RDO. I
loved ADO when it came out and quickly switched all my programs to use it.
>
I've tried to make the switch to ADO.NET, but just can't seem to figure
out what I'm doing most of the time. I'm using it in just a couple of
forms where I needed it to work with a DataGridView and to update a few
records.
>
Am I the only stupid one out there that would rather use the old ADO? Is
there an easy way to learn ADO.NET?

[kimiraikkonen]

Re: ADO.NET vs ADO

On Oct 18, 4:35 am, Kevinp <kev...@nospam. comwrote:

Just a silly question probably...
>
I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using 2008. When I started programming, VB5 was just out and I was using RDO. I loved ADO when it came out and quickly switched all my programs to use it.
>
I've tried to make the switch to ADO.NET, but just can't seem to figure out what I'm doing most of the time. I'm using it in just a couple of forms where I needed it to work with a DataGridView and to update a few records.
>
Am I the only stupid one out there that would rather use the old ADO? Is there an easy way to learn ADO.NET?

Hi,
You can look at the architechture comparision:

http://en.wikipedia.org/wiki/ADO_vs_ADO.NET

http://www.startvbdotnet.com/ado/default.aspx

http://www.devarticles.com/c/a/ADO.NET/A-Practical-Comparison-of-ADO-and-ADO.NET/

http://msdn.microsoft.com/en-us/library/ms973217.aspx

After you decided which one to use, you can find more articles about
the selected platform, however, as ADO.NET came with .NET platform, it
would be much wiser to start and continue with managed ADO.NET,
however if your existing application is based on classic ADO, you
still have the chance to add reference to "Microsoft ActiveX Data
Objects Library" using ADODB namespace. However i don't have much
experience about manipulating legacy ADO classes in .NET platform.
Anyway, the procedure logics are similar, there must be different or
easier approaches in ADO.NET.

Hope this helps,

Onur Güzel

[Paul Engel]

Re: ADO.NET vs ADO

I felt the same way. Then I bought a great book on it and fell in love with
it. It is a COMPLETELY different model, though, so you have to view it as
such. It's a disconnected dataset. I love the idea of the collection of rows
and columns that you can pass to procedures. The keys, as I see them are:
- Always return a unique key for any record that needs to be updated
- Use SQL update, add, delete statements passed back through and existing or
new connection to alter the original data source.
- If you can, write a data access object of your own that you can pass a few
arguments that can consistantly deal w/ the ADO.Net work against any type of
database you choose to work with. The book was Wrox ADO.Net with VB.Net,
version 2. I think it may be out of print. But, they actually included the
data access class w/ the sample code and I have modified it and use it
EXTENSIVELY!

You'll LOVE it once you shift your brain to the new model.


"Kevinp" <kevinp@nospam. comwrote in message
news:4i9if41c7c rojv10pkhmt9v8h p4o2dk1fg@4ax.c om...

Just a silly question probably...
>
I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using
2008. When I started programming, VB5 was just out and I was using RDO. I
loved ADO when it came out and quickly switched all my programs to use it.
>
I've tried to make the switch to ADO.NET, but just can't seem to figure
out what I'm doing most of the time. I'm using it in just a couple of
forms where I needed it to work with a DataGridView and to update a few
records.
>
Am I the only stupid one out there that would rather use the old ADO? Is
there an easy way to learn ADO.NET?

[Kevinp]

Re: ADO.NET vs ADO

I'll see if I can find it. Thanks.

And thanks to everyone else for your replies.

Kevin


On Sat, 18 Oct 2008 11:32:54 -0400, "Paul Engel" <paul.engel@veb ridge.comwrote:

>I felt the same way. Then I bought a great book on it and fell in love with
>it. It is a COMPLETELY different model, though, so you have to view it as
>such. It's a disconnected dataset. I love the idea of the collection of rows
>and columns that you can pass to procedures. The keys, as I see them are:
>- Always return a unique key for any record that needs to be updated
>- Use SQL update, add, delete statements passed back through and existing or
>new connection to alter the original data source.
>- If you can, write a data access object of your own that you can pass a few
>arguments that can consistantly deal w/ the ADO.Net work against any type of
>database you choose to work with. The book was Wrox ADO.Net with VB.Net,
>version 2. I think it may be out of print. But, they actually included the
>data access class w/ the sample code and I have modified it and use it
>EXTENSIVELY!
>
>You'll LOVE it once you shift your brain to the new model.
>
>
>"Kevinp" <kevinp@nospam. comwrote in message
>news:4i9if41c7 crojv10pkhmt9v8 hp4o2dk1fg@4ax. com...

>Just a silly question probably...
>>
>I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using
>2008. When I started programming, VB5 was just out and I was using RDO. I
>loved ADO when it came out and quickly switched all my programs to use it.
>>
>I've tried to make the switch to ADO.NET, but just can't seem to figure
>out what I'm doing most of the time. I'm using it in just a couple of
>forms where I needed it to work with a DataGridView and to update a few
>records.
>>
>Am I the only stupid one out there that would rather use the old ADO? Is
>there an easy way to learn ADO.NET?

>

[Scott M.]

Re: ADO.NET vs ADO

Others have mentioned some good resources, but I'd like to address the
benefits of ADO .NET vs. the pitfalls of ADO.

First, using ADO in .NET will inherantly cause performance problems as you
will be utilizing COM architecture in .NET. So, right away you are at a
disadvantage and will never see the best performing code you could have
using ADO in .NET.

Second, ADO was, by default, a "connected" paradigm and while you could
indicate you wanted to work with client-side cursors, it made the coding
much more complex.

Third, ADO was very limited in the kinds of operations you could perfom on /
with your data (ie. one RecordSet was isolated from another).

ADO .NET is all about working with disconnected data, by default, with some
very good options available for working in a connected mode. It has a very
heirarchical model, which follows the logical structure of a relational
database.

Sure, because the model is bigger, it can also be more complex than ADO, but
that doesn't mean ADO is better.

My advice, when moving to .NET from the "classic" technologies is, honestly,
to forget what you know and approach .NET programming as a completely new
paradigm. If you try to learn .NET from a standpoint of "How does this
releate to what I already know?", you will invariably get a brain-cramp.

-Scott

"Kevinp" <kevinp@nospam. comwrote in message
news:4i9if41c7c rojv10pkhmt9v8h p4o2dk1fg@4ax.c om...

Just a silly question probably...
>
I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using
2008. When I started programming, VB5 was just out and I was using RDO. I
loved ADO when it came out and quickly switched all my programs to use it.
>
I've tried to make the switch to ADO.NET, but just can't seem to figure
out what I'm doing most of the time. I'm using it in just a couple of
forms where I needed it to work with a DataGridView and to update a few
records.
>
Am I the only stupid one out there that would rather use the old ADO? Is
there an easy way to learn ADO.NET?

[Cor Ligthert[MVP]]

Re: ADO.NET vs ADO

Aaron,

Now some people are talking in sentences as better or whatever.

Ado is not created to work on real hugh networks. It was made for LAN's with
a througput from 2Kb and therefore had limited users.

However although I had never a reason to do that, can sometimes Ado "the
recordset" (and even more Dao) technical be a better solution than AdoNet
on a Win32 enviroment, be aware however that this will be in very limited
situations and the change that it happens once to you is low.

jmo

Cor


"Kevinp" <kevinp@nospam. comwrote in message
news:4i9if41c7c rojv10pkhmt9v8h p4o2dk1fg@4ax.c om...

Just a silly question probably...
>
I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using
2008. When I started programming, VB5 was just out and I was using RDO. I
loved ADO when it came out and quickly switched all my programs to use it.
>
I've tried to make the switch to ADO.NET, but just can't seem to figure
out what I'm doing most of the time. I'm using it in just a couple of
forms where I needed it to work with a DataGridView and to update a few
records.
>
Am I the only stupid one out there that would rather use the old ADO? Is
there an easy way to learn ADO.NET?

[Michel Posseth [MCP]]

Re: ADO.NET vs ADO



I had not so much trouble adopting ADO.Net and have never written anny ADODB
code in a .Net environment
and that while my first coding experiences where in the mid eighty`s on a
CBM64 .

I honestly believe that anny coder can be up and running with ADO.Net in
just a few hours you just need a good coding reference
so do yourself a favor and buy yourself a good ADO.Net reference book . I
would recomend you the following writers Bill Vaughn , Francesco Balena ,
David Sceppa .


And if you encounter anny problems you can`t solve yourself there is always
someone here in these groups for assistance


regards

Michel Posseth

http://www.vbdotnetcoder.com

"Scott M." <s-mar@nospam.nosp amschreef in bericht
news:eMdbiKtMJH A.4600@TK2MSFTN GP06.phx.gbl...

Others have mentioned some good resources, but I'd like to address the
benefits of ADO .NET vs. the pitfalls of ADO.
>
First, using ADO in .NET will inherantly cause performance problems as you
will be utilizing COM architecture in .NET. So, right away you are at a
disadvantage and will never see the best performing code you could have
using ADO in .NET.
>
Second, ADO was, by default, a "connected" paradigm and while you could
indicate you wanted to work with client-side cursors, it made the coding
much more complex.
>
Third, ADO was very limited in the kinds of operations you could perfom on
/ with your data (ie. one RecordSet was isolated from another).
>
ADO .NET is all about working with disconnected data, by default, with
some very good options available for working in a connected mode. It has
a very heirarchical model, which follows the logical structure of a
relational database.
>
Sure, because the model is bigger, it can also be more complex than ADO,
but that doesn't mean ADO is better.
>
My advice, when moving to .NET from the "classic" technologies is,
honestly, to forget what you know and approach .NET programming as a
completely new paradigm. If you try to learn .NET from a standpoint of
"How does this releate to what I already know?", you will invariably get a
brain-cramp.
>
-Scott
>
"Kevinp" <kevinp@nospam. comwrote in message
news:4i9if41c7c rojv10pkhmt9v8h p4o2dk1fg@4ax.c om...

>Just a silly question probably...
>>
>I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using
>2008. When I started programming, VB5 was just out and I was using RDO. I
>loved ADO when it came out and quickly switched all my programs to use
>it.
>>
>I've tried to make the switch to ADO.NET, but just can't seem to figure
>out what I'm doing most of the time. I'm using it in just a couple of
>forms where I needed it to work with a DataGridView and to update a few
>records.
>>
>Am I the only stupid one out there that would rather use the old ADO? Is
>there an easy way to learn ADO.NET?

>
>

[Cor Ligthert[MVP]]

Re: ADO.NET vs ADO

Michel,

Scott is as well a long time contributer too the ADO.Net newsgroup, like
Bill Vaughn, in past David Sceppa and I.

Cor

"Michel Posseth [MCP]" <MSDN@posseth.c omwrote in message
news:%23hTMJCuM JHA.4772@TK2MSF TNGP03.phx.gbl. ..

>
>
I had not so much trouble adopting ADO.Net and have never written anny
ADODB code in a .Net environment
and that while my first coding experiences where in the mid eighty`s on a
CBM64 .
>
I honestly believe that anny coder can be up and running with ADO.Net
in just a few hours you just need a good coding reference
so do yourself a favor and buy yourself a good ADO.Net reference book . I
would recomend you the following writers Bill Vaughn , Francesco Balena ,
David Sceppa .
>
>
And if you encounter anny problems you can`t solve yourself there is
always someone here in these groups for assistance
>
>
regards
>
Michel Posseth

http://www.vbdotnetcoder.com

>
>
>
>
>
>
"Scott M." <s-mar@nospam.nosp amschreef in bericht
news:eMdbiKtMJH A.4600@TK2MSFTN GP06.phx.gbl...

>Others have mentioned some good resources, but I'd like to address the
>benefits of ADO .NET vs. the pitfalls of ADO.
>>
>First, using ADO in .NET will inherantly cause performance problems as
>you will be utilizing COM architecture in .NET. So, right away you are
>at a disadvantage and will never see the best performing code you could
>have using ADO in .NET.
>>
>Second, ADO was, by default, a "connected" paradigm and while you could
>indicate you wanted to work with client-side cursors, it made the coding
>much more complex.
>>
>Third, ADO was very limited in the kinds of operations you could perfom
>on / with your data (ie. one RecordSet was isolated from another).
>>
>ADO .NET is all about working with disconnected data, by default, with
>some very good options available for working in a connected mode. It has
>a very heirarchical model, which follows the logical structure of a
>relational database.
>>
>Sure, because the model is bigger, it can also be more complex than ADO,
>but that doesn't mean ADO is better.
>>
>My advice, when moving to .NET from the "classic" technologies is,
>honestly, to forget what you know and approach .NET programming as a
>completely new paradigm. If you try to learn .NET from a standpoint of
>"How does this releate to what I already know?", you will invariably get
>a brain-cramp.
>>
>-Scott
>>
>"Kevinp" <kevinp@nospam. comwrote in message
>news:4i9if41c7 crojv10pkhmt9v8 hp4o2dk1fg@4ax. com...

>>Just a silly question probably...
>>>
>>I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using
>>2008. When I started programming, VB5 was just out and I was using RDO.
>>I loved ADO when it came out and quickly switched all my programs to use
>>it.
>>>
>>I've tried to make the switch to ADO.NET, but just can't seem to figure
>>out what I'm doing most of the time. I'm using it in just a couple of
>>forms where I needed it to work with a DataGridView and to update a few
>>records.
>>>
>>Am I the only stupid one out there that would rather use the old ADO? Is
>>there an easy way to learn ADO.NET?

>>
>>

>
>

[Michel Posseth [MCP]]

Re: ADO.NET vs ADO


Was it so unclear that my previous answer was for the TS as followowup to
Scott`s answer ?

Yes i know who Scott is ( although his virtual alter ego ) :-) and with his
answer to the TS he sure doesn`t need anny of my advices


"Cor Ligthert[MVP]" <Notmyfirstname @planet.nlschre ef in bericht
news:%23n4rvPzM JHA.1160@TK2MSF TNGP04.phx.gbl. ..

Michel,
>
Scott is as well a long time contributer too the ADO.Net newsgroup, like
Bill Vaughn, in past David Sceppa and I.
>
Cor
>
"Michel Posseth [MCP]" <MSDN@posseth.c omwrote in message
news:%23hTMJCuM JHA.4772@TK2MSF TNGP03.phx.gbl. ..

>>
>>
>I had not so much trouble adopting ADO.Net and have never written anny
>ADODB code in a .Net environment
>and that while my first coding experiences where in the mid eighty`s on a
>CBM64 .
>>
>I honestly believe that anny coder can be up and running with ADO.Net
>in just a few hours you just need a good coding reference
>so do yourself a favor and buy yourself a good ADO.Net reference book .
>I would recomend you the following writers Bill Vaughn , Francesco Balena
>, David Sceppa .
>>
>>
>And if you encounter anny problems you can`t solve yourself there is
>always someone here in these groups for assistance
>>
>>
>regards
>>
>Michel Posseth
>http://www.vbdotnetcoder.com
>>
>>
>>
>>
>>
>>
>"Scott M." <s-mar@nospam.nosp amschreef in bericht
>news:eMdbiKtMJ HA.4600@TK2MSFT NGP06.phx.gbl.. .

>>Others have mentioned some good resources, but I'd like to address the
>>benefits of ADO .NET vs. the pitfalls of ADO.
>>>
>>First, using ADO in .NET will inherantly cause performance problems as
>>you will be utilizing COM architecture in .NET. So, right away you are
>>at a disadvantage and will never see the best performing code you could
>>have using ADO in .NET.
>>>
>>Second, ADO was, by default, a "connected" paradigm and while you could
>>indicate you wanted to work with client-side cursors, it made the coding
>>much more complex.
>>>
>>Third, ADO was very limited in the kinds of operations you could perfom
>>on / with your data (ie. one RecordSet was isolated from another).
>>>
>>ADO .NET is all about working with disconnected data, by default, with
>>some very good options available for working in a connected mode. It
>>has a very heirarchical model, which follows the logical structure of a
>>relational database.
>>>
>>Sure, because the model is bigger, it can also be more complex than ADO,
>>but that doesn't mean ADO is better.
>>>
>>My advice, when moving to .NET from the "classic" technologies is,
>>honestly, to forget what you know and approach .NET programming as a
>>completely new paradigm. If you try to learn .NET from a standpoint of
>>"How does this releate to what I already know?", you will invariably get
>>a brain-cramp.
>>>
>>-Scott
>>>
>>"Kevinp" <kevinp@nospam. comwrote in message
>>news:4i9if41c 7crojv10pkhmt9v 8hp4o2dk1fg@4ax .com...
>>>Just a silly question probably...
>>>>
>>>I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using
>>>2008. When I started programming, VB5 was just out and I was using RDO.
>>>I loved ADO when it came out and quickly switched all my programs to
>>>use it.
>>>>
>>>I've tried to make the switch to ADO.NET, but just can't seem to figure
>>>out what I'm doing most of the time. I'm using it in just a couple of
>>>forms where I needed it to work with a DataGridView and to update a few
>>>records.
>>>>
>>>Am I the only stupid one out there that would rather use the old ADO?
>>>Is there an easy way to learn ADO.NET?
>>>
>>>

>>
>>

>