|
|
|
|
|
|
|
|
|
|
- Overview
- Summary diagram
- Remarks
A window or page can display information coming from: - a database: controls are directly bound to the items in the data files or queries available in the database.
- variables in the application's code (variables global to the window, page or project, class members, etc.).
- members or properties of .Net objects.
- .Net Object variables (to WLanguage arrays containing.Net Objects).
To display this information in a window or page, the controls in the window or page must be bound to: - the different items in the database.
- the available WLanguage variables (Data binding).
There are multiple methods to display and update values from a data source: The following diagram shows a summary of the bindings between controls and data:
- When dragging and dropping an item or variable onto a page or window, the corresponding control is automatically created with the corresponding binding.
For more details on data binding, see Data binding from the "Project explorer" pane. - Most types of controls can be bound to an item in a data file or variable. For more details on the types of controls, see the online documentation.
- Data binding on Table controls requires special management: Table controls based on variables are not handled as Table controls based on data files. For more details, see Specific features of data binding on Table controls.
- Limitations:
- Two-dimensional WLanguage arrays cannot be used for data binding.
- Associative arrays cannot be used for data binding.
Related Examples:
|
Training (WINDEV): WD DataBinding
[ + ] The "WD DataBinding" example explains how to link a control and a WLanguage variable. This example includes two windows: - A first window presents a simple link between the controls and a composite variable. - A second window presents a link between a table control and a WLanguage class as well as the link between the table and a detailed form
|
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|