Quote Originally Posted by RhinoBull
I don't believe in data binding even though .net has added a sort of different meaning to it.
It doesn't take much to populate grid "manually".
Let's say that you have a read-only grid to display data and a set of TextBoxes, etc. to update data. You would have to populate the grid, update the other controls when the grid selection changes, validate the data entered into the other controls, update the grid when the data was edited in the other controls, add new objects when rows are added and delete objects when rows were deleted. Data-binding can do all of that for you with essentially no code. I'm aware that there were arguments against using data-binding in VB6, but to the best of my knowledge those arguments were specific to the way VB6 implemented data-binding. It's quite different in VB.NET by virtue of the fact that ADO.NET is disconnected. Some may also argue that not using data-binding gives you more control, but I always use data-binding where possible and I have complete control over how my data and UI behave. To each their own, and I'd certainly not say that people must use data-binding, but I can't personally see an advantage to not. It's a big time-saver and cuts down on the amount of code you have to maintain.