ADO.NET Sucks

[Adam Clark]

I am having problems with ADO.NET

I need a constant connection between my VB application and my sql
database... can I use anything else other than legacy ADO? Does anyone know
if microsoft is going to change ADO.NET so we can go back to realtime access
to the database and not use datasets?

Thanks

Respectfully, Adam W Clark 812-552-1170 "That'll do donkey.. That'll do."

[Peter Proost]

Why do you need a constant connection?

Greetz Peter

"Adam Clark" <ad*******@netscape.com> schreef in bericht
news:%2****************@TK2MSFTNGP12.phx.gbl...

I am having problems with ADO.NET

I need a constant connection between my VB application and my sql
database... can I use anything else other than legacy ADO? Does anyone know if microsoft is going to change ADO.NET so we can go back to realtime access to the database and not use datasets?

Thanks

Respectfully, Adam W Clark 812-552-1170 "That'll do donkey.. That'll do."

[David Browne]

"Adam Clark" <ad*******@netscape.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

I am having problems with ADO.NET

I need a constant connection between my VB application and my sql
database... can I use anything else other than legacy ADO? Does anyone
know if microsoft is going to change ADO.NET so we can go back to realtime
access to the database and not use datasets?

Nothing is stopping you from opening a persistent connection to the
database, and no one is forcing you to use datasets. What's the problem?

David

[Bernie Yaeger]

Hi Adam,

That was my initial reaction to ado .net. But after working with it for a
while, I now consider it far superior to - admittedly more difficult than -
ado. The only real problem is loading a large - I mean large: 35 cols,
750,000 rows - table in one shot. But I have almost always been able to
find workarounds. Its disconnected state is wonderful and, for all intents
and purposes, user clashes are gone.

Bernie Yaeger

"Adam Clark" <ad*******@netscape.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

I am having problems with ADO.NET

I need a constant connection between my VB application and my sql
database... can I use anything else other than legacy ADO? Does anyone
know if microsoft is going to change ADO.NET so we can go back to realtime
access to the database and not use datasets?

Thanks

Respectfully, Adam W Clark 812-552-1170 "That'll do donkey.. That'll do."

[Carlos J. Quintero [.NET MVP]]

a) You can use a permanent conection, nothing in ADO.NET prevents that.

b) You can avoid datasets and use only Command and DataReader objects.

I think that you have read only the portion of ADO.NET that deals with
disconnected scenarios.

--

Carlos J. Quintero

MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com

I need a constant connection between my VB application and my sql
database... can I use anything else other than legacy ADO? Does anyone
know if microsoft is going to change ADO.NET so we can go back to realtime
access to the database and not use datasets?

[Herfried K. Wagner [MVP]]

"Adam Clark" <ad*******@netscape.com> schrieb:

I am having problems with ADO.NET

=> microsoft.public.dotnet.framework.adonet

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[Cor Ligthert]

Adam,

AdoNet does not suck.

AdoDB is constantly sucking on the databases and therefore those can become
in problem when their triggers get overloaded.

Probably I don't understand what you want.

Cor