Data Binding


Create new tables with fields that match the controls on your UX Component, or bind the controls in your UX Component to fields in existing tables. The Data Binding page lets you bind an entire UX component to new or existing SQL or DBF tables in a database and then assign controls to fields in those table accordingly.

Create new table(s) to match the controls on your UX component

Creates tables for existing controls in the UX Component. The new tables and fields will match the controls in the UX. Use this command if you have designed a UX component and would now like to create table(s) that match the structure of your UX. Once you have created table(s) to match the structure of your UX, you will be able to add code int he 'afterDialogValidate' event to save the data that the user submits to one or more tables.

Bind the controls on your UX to fields in one or more existing tables.

This page contains two main parts. The first part allows you to bind an existing table, or tables, from a database to the UX component. The second part lets you map, or "bind", controls in the UX component to fields in the existing table(s). This binding can also be done from the [Data Binding properties] section of individual controls on the UX Controls page.

Specify Primary Keys and Sequences

Specify the primary key and other table properties for each table that the UX Component is data bound.

Permissions and Security

Set the permissions and security groups for insert, update, and delete operations for a data bound UX Component.

Refresh table information after editing table schema(s)

Refresh the table structure information that is stored for a data bound UX component. Required if table fields are added or field types are changed.

Remove all Data Binding settings

Deletes the data binding settings from the UX component.

You also do data binding when you create a Detail View from an SQL database inside a List Control. When you define the Detail view you specify that certain data controls should be bound to selected fields in the SQL table that the list is linked to. For example, in order to form the Detail View you might bind textbox control on your component named 'City' to a field in an SQL database name 'City'. This is 'data binding'. Once you do this, the data bound list control will appear on the Data Binding page's 'Summary' section, as demonstrated by the image below.

A summary showing a List Detail-View with data binding

One advantage of using the detail view of a list for data binding is that you are can do CRUD (create, read, update, delete) operations against two independent and unlinked tables from inside the same UX component. This as opposed to having one table or group of tables linked directly to the component itself. The difference between these two models of data binding is explained in this video. If you do, in fact, want to link your entire UX component to a given SQL or DBF database, you can do this using the options available on the data binding page.

A summary showing a component with data binding