Datagrids suck! Why was VB6 so bad!?!?

[HollywoodKY]

I'm really frustrated and I'm hoping you guys know of a way to make this work. VB6 allowed me to use recordsets and ADO libraries and I loved it. Now with .Net, it appears everyone is using this ridiculous datagrid control. I hate it. Maybe its because I don't know how to use it efficiently, so help me out.

I don't want to see my database in a table. That's lame and inefficient. I just want to be able to load my Access DB into an adapter and then navigate the database via buttons and fill textboxes with the relevant data from the database. I then want to be able to edit them as I did in VB6. Maybe its just me, but I HATE how .Net handles DB's now. What was so wrong with the other way? I'm developing a stand-alone app that requires no use of the Internet, so why couldn't they leave that library in for this purpose?

If you're wondering why I don't just use VB6, its because I like the added controls and option of "updating" my programs with online functionality... SHOULD I CHOOSE TO DO SO!

Help me out guys... convert this non-believer... and don't tell me to use a datagrid!!! How gay...


HWOODKY

[stingrae]

i know what you're referring to in terms of frustration. there;s at least 100 other threads on this topic too.

all i can suggest is download my ebook from here www.stingrae.com.au and see if that helps you at all

[DevGrp]

Originally posted by HollywoodKY
I'm really frustrated and I'm hoping you guys know of a way to make this work. VB6 allowed me to use recordsets and ADO libraries and I loved it. Now with .Net, it appears everyone is using this ridiculous datagrid control. I hate it. Maybe its because I don't know how to use it efficiently, so help me out.

I don't want to see my database in a table. That's lame and inefficient. I just want to be able to load my Access DB into an adapter and then navigate the database via buttons and fill textboxes with the relevant data from the database. I then want to be able to edit them as I did in VB6. Maybe its just me, but I HATE how .Net handles DB's now. What was so wrong with the other way? I'm developing a stand-alone app that requires no use of the Internet, so why couldn't they leave that library in for this purpose?

If you're wondering why I don't just use VB6, its because I like the added controls and option of "updating" my programs with online functionality... SHOULD I CHOOSE TO DO SO!

Help me out guys... convert this non-believer... and don't tell me to use a datagrid!!! How gay...


HWOODKY

Actually the DataGrid is quite powerfull and very flexible. But before you start pulling your hair out, I suggest getting a book on ADO.NET. You'll really start to appreciate the new data model once you understand it a little better.

Anywhat, what you are talking about can be done very easy with databinding and the bindingcontext method. You can download the 101 VB.NET code samples from MS here http://download.microsoft.com/downlo...netsamples.exe and check out this project 'VB.NET - Data Access - Create an Offline Application'. It has exactly what you are looking for.

Good luck

[Slow_Learner]

You are far from stuck with using datagrid with datasets, I use ListView with datatables all the time and I'm quite happy with it for situations where I don't want the user directly editing fields but I want a nice tabular display of stuff. Take a look at this thread:

http://www.vbforums.com/showthread.p...t=xml+listview

Example code for putting a datatable's contents into a listview programatically.