My 20+ years experience is primarily VB6 and MS Access and working with various backends and devices.
In VB2005 i have started a project.
On the left i see "Database Explorer", and on the right is "Data Connections".
Questions:
Do I always have to use one or both of those things?
I just wanna have a connection ready to use at all times to my database.
I'm not real sure about why I would want to use a DataSet.
I'm thinking that I want to read or write to the real tables.
So a DataReader is only good for read-only?
Many of the aricles/books I read talk about the different "Core Objects" in ADO.NET.
It's like openning a toolbox in an extraterestrial spaceship's garage.
Can't figure out what the hell to do with some of these new-fangled widgets.
All this "ADO.NET is more better" kind of talk is very confusing.
It's obviously (to me) not any easier or simpler.
It's not making my life better.
Maybe I'm just not drinking the right kool-aid.
-------------------
The greatest obstacle to discovery is not ignorance -- it is the illusion of knowledge.
Daniel Boorstin
In VB2005 i have started a project.
On the left i see "Database Explorer", and on the right is "Data Connections".
Questions:
Do I always have to use one or both of those things?
I just wanna have a connection ready to use at all times to my database.
I'm not real sure about why I would want to use a DataSet.
I'm thinking that I want to read or write to the real tables.
So a DataReader is only good for read-only?
Many of the aricles/books I read talk about the different "Core Objects" in ADO.NET.
It's like openning a toolbox in an extraterestrial spaceship's garage.
Can't figure out what the hell to do with some of these new-fangled widgets.
All this "ADO.NET is more better" kind of talk is very confusing.
It's obviously (to me) not any easier or simpler.
It's not making my life better.
Maybe I'm just not drinking the right kool-aid.
-------------------
The greatest obstacle to discovery is not ignorance -- it is the illusion of knowledge.
Daniel Boorstin