Printable View
In VB6.0 data binding was setting a textbox's datasource to a datacontrol (or something sort of... It's about using data-bound controls), is it still the way it's done in VB.Net? I havent actually done database stuff yet but it seems I often read about data binding in here? In VB6.0 I never really bind or use any data-bound control so I wish to be clarified about this case in VB.Net...
Data-binding involves linking the data displayed in a control to some other source. The data source is most often a DataTable, either stand-alone or part of a DataSet, or a whole DataSet in the case of some DataGrids. It can be other objects though, like an array or collection. The beauty of data-binding is that you can programatically alter the underlying data source and the changes will be refelected in the control, and the user can alter the data in the control and the changes will be reflected in the data source. There is no need to laboriously fill a control using loops or retrieve the edited data when done. Basically, data-binding is a really, really good thing.
It most certainly is in VB 2005 Express Edition Beta 2! However, it is more advanced than before, allowing you to open a dialog in order to set the bindings to just about anything you can imagine - even to bind it to other properties in order to extend functionality.Quote:
Originally Posted by dee-u
Quote:
Originally Posted by MSDN Express
I noticed I even have a link in my signature (Data Binding Is Evil), if you will care to read would you tell me that it doesn't apply to VB.Net? I just want to be enlightened...
It sounds to me like VB6 data binding and VB.NET data binding are two quite different things. They seem to be saying that ADO is a better alternative to data binding, but ADO.NET is not an alternative to data binding in .NET. Rather the two work together to make data access easier and quicker. Like any technology that hides complexity, it can make programmers lazy to a certain degree. Many people use data binding without really understandaing what it is they are doing. I would highly recommend that you understand data binding and how it works, as well as the alternatives, but feel more than free to use data binding in VB.NET wherever it is appropriate.
It's somewhat really confusing as I've havent really started doing database stuff with VB.Net (I'll soon do, with a small app I will convert from VB6.0 to Vb.Net), so you would recommend that I would use data-binding in VB.Net? It seems it was easier (in VB6.0) not to use data-binding, well I had experienced data-binding in the early part of my learning process of VB6.0 and I encountered lots of troubles with it, when I junk it then all became smooth for me so I want to know what would be the advantages and disadvantages of employing data-binding in VB.Net to clarify things up...
Like I said, data binding creates a two way relationship between a data source and a control, which negates the need for you to manually transfer data form a data source to a control initially and then back again after editing. When I say "data source" I mean an object in memory, not the actual database. To be used properly in all instances there is still a reasonable amount to know about data binding in .NET, but if done properly it will simplify your life greatly. Use it.
In VB6.0 when I used to bind my controls to data controls the main problem I could remember was when trying to modify a certain textbox then tried to close the form the changes are automatically reflected in the database, so is moving to the next record, the changes are automatically saved, is it the same case in VB.Net?
Data binding in VB.NET knows nothing of the database itself. You are binding your controls to objects in memory. Usually those objects will be individual DataTables or a DataSet. Any changes you make in the bound controls will be reflected in that data source, but the database itself is, as always, disconnected from that data and is not updated until you explicitly do so.Quote:
Originally Posted by jmcilhinney