Data Bounds controls vs SQL statements

  • Thread starter Thread starter Alexey Maykov
  • Start date Start date
A

Alexey Maykov

Obviously, there are two strategoies of developing UIs for manipulating data
from SQL server. First is based on data-bound controls, the second one is
based on regular controls (DB-agnostic) and using SQL statements to
manipulate data. What are pluses or minuses of both?

It seems to me that data-bound controls are more suitable for quick
porotyping and for developers unfamiliar with SQL, while developing apps in
conventional way (with SQL queries) reqiures more effort but allows for more
flexibility/control.
 
If you want to use databinding, there are two posibilities: simple and
complex databinding. The first form of databinding binds a single property
of one object to a property of a second object. The second form of
databinding allows you to work with lists (tables), and can be used with any
object that implements IList. As you can see, databinding really is
independent of ADO.NET and as such there is little, if any, connection to
databases. An example of complex databinding is a DataGrid control that is
bound to a DataTable in a DataSet.

To understand these issues, you need to gain a deeper understanding of
ADO.NET, and how it is divided into two groups of classes: disconnected and
connected classes. After this you can look into databinding.
 
Back
Top