Data Binding Web Forms List Controls

MM .NET Web Forms list controls implement the ImmWebBinding and ImmWebBindingList interfaces, which possess the following custom binding properties:

  • BindingSource - Name of the binding source business object. You can use the MM .NET Binding Source Selection dialog to set this property.

  • BindingSourceDisplayMember - The member of the data source you want to display. You can use the MM .NET Binding Source Member Selection dialog to easily set this property.

      • FieldName

      • DataTableName.FieldName

      • DataTableName.DataViewName.FieldName

  • BindingSourceValueMember - The member of the data source from which to draw the value. You can use the MM .NET Binding Source Member Selection dialog to easily set this property.

      • FieldName

      • DataTableName.FieldName

      • DataTableName.DataViewName.FieldName

    If you have a one-part name, it specifies the field name of the business object's default DataSet.

    If you have a two-part name, it specifies the DataTable and field of the business object's default DataSet

    If you have a three-part name, it specifies the control is bound to the field of a DataView belonging to the specified DataTable of the business object's default DataSet. If the name of the view is "DefaultView", then the control is bound to the default view of the DataTable. To use anything other than the DefaultView, the associated DataSet must be an mmDataSet.

  • BindingType - Specifies the type of binding to be applied to the control:

    • None
    • OneWay
    • TwoWay

  • BindingValueSource - The name of the source business object class to bind the SelectedValue property of this control. You can use the MM .NET Binding Source Selection dialog to set this property.

  • BindingValueSourceMember - The member of the binding value source you want to bind to. You can use the MM .NET Binding Source Member Selection dialog to easily set this property.

See Also:
Data Binding MM .NET Windows Forms Controls


© (c) 2026 Oak Leaf Enterprises, Inc., 1996-2026 • Updated: 04/13/17
Comment or report problem with topic