Re: ADO (ActiveX) data binding to .NET Windows Form controls
From: Val Mazur (group51a_at_hotmail.com)
Date: 04/17/04
- Next message: andrewcw: "grid heiracheal display"
- Previous message: Ray Cassick \(Home\): "Re: .net 1.1"
- Maybe in reply to: Marcin Floryan: "ADO (ActiveX) data binding to .NET Windows Form controls"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 16 Apr 2004 22:50:05 -0400
Hi,
ADO .NET is not oriented to SQL Server. OLEDB .NET Managed provider works
with any compatible OLEDB provider (including Jet). There are some
additional providers, which target specific servers, like SQL Server or
Oracle, but these providers just provide additional functionality, not
prevent you from using Jet or other standard OLEDB providers. Using
COM-based ADO or other COM components, just adds additional layer into your
application, which slows down it. You will not gain anything using ADO under
.NET environment. I know from my own experience that using ADO.NET at the
beginning is not so easy, because it looks totally different from what ADO
has, but finally it is much better than ADO and gives you more
possibilities. Updating could be done in different ways and it is much
flexible as well, since you could specify specific command to update your
database.
You do not have to retrieve all the data to open DataSet. You just select
what you need. This is true for ADO as well. If you open the whole table in
ADO, then it is bad as well.
Yu also could keep your connection opened during session and you do not have
to close it, but since ADO.NET provider pooling of the connections, you will
not see any performance impact if you open and close your connection
constantly.
I know it takes some time, but it worth to invest this time to get better
results.
-- Val Mazur Microsoft MVP "Marcin Floryan" <marcin[REMOVE]@floryan.neostrada.pl> wrote in message news:%235sr9QsIEHA.3572@TK2MSFTNGP10.phx.gbl... > > "Val Mazur" <group51a@hotmail.com> wrote in message > news:OZGK0SpIEHA.3240@TK2MSFTNGP12.phx.gbl... >> Hi Marcin, >> >> What is the reason to use ADO under .NET environment? You will not get >> any >> advantage. Use VB6 instead. >> Otherwise, if you decided to go with .NET, use ADO.NET. > > What if I own VS and do not have VB6, that's the company's choice not > mine. > > I use ADO because it is by far more simple to use then ADO.NET and works > smoothly with Microsoft Access DB via JET. > ADO.NET is targeted on accessing SQL server mainly and I find using MS > Access with ADO.NET being rather akward. I don't like the idea of having > to > copy the entire table into a DataSet. Also there is much more fuss when I > want to update. With ADO I just change values and do rst.Update while with > ADO.NET I have to issue commands and data is not updated on the spot. > Another thing is that I want to have a persistant open connection with my > database and I want this database locked rather then opening it every time > data changes. What's more, I feel there is some overhead when accessing MS > Access DB form ADO.NET if I compare to ADO. > >> Another suggestion is to avoid using of the bound controls at all. >> It just adds some extra issues to your code and you do not know what is >> going on inside. > > Yes, thank you - I have already done so. This is true that data binding is > more fuss than gain. But then again, why to have a feature like this when > it's useless. > > Best regards, and thank you for your comment. > > Marcin Floryan > >
- Next message: andrewcw: "grid heiracheal display"
- Previous message: Ray Cassick \(Home\): "Re: .net 1.1"
- Maybe in reply to: Marcin Floryan: "ADO (ActiveX) data binding to .NET Windows Form controls"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
