ADO in VB.NET

[Sean]

What is the difference between the ADODB .NET reference
and the MDAC 2.7 COM object? Should I be moving away from
using the COM objects like I did in VB 6.0 and using
the .NET?

 

[Cor]

Hi Sean,

If you should is your own decission,

I would

Cor

 

[One Handed Man [ OHM# ]]

Dont forget that in ADO.NET, you are working in a disconnected environment.
This is great for some applications, but is not suited to others where many
users are working in an interactive database application where record
locking is needed for example. There are ways around this but they nefarious
to say the least.

Regards - OHM

----------------

 

[Sean]

But what is the difference? Is it using the same
underlying components, but one is wrapped in a COM object
and one an assembly? (Bare with me I'm new to .NET) Thanks!

 

[Cor]

Hi Sean,

It is a totaly different approach.

But look also at the message from OHM.

And I would ask this also in the active newsgroup
Microsoft.public.dotnet.framework.adonet

That is more the place for questions about this and you have a change on
more answers
(If it was how to use it with the VB.net language code I think this is also
the right newsgroup)

Cor

 

[Herfried K. Wagner [MVP]]

What is the difference between the ADODB .NET reference
and the MDAC 2.7 COM object? Should I be moving away from
using the COM objects like I did in VB 6.0 and using
the .NET?

Yes, ADO.NET is preferred (you don't need any references to COM
components to use it). More info:

<
Web interface:

<http://msdn.microsoft.com/newsgroup...roup=microsoft.public.dotnet.framework.adonet>