Unless the graphical object is a static object and has a specific and unique purpose such as a Line, it requires binding to an existing attribute as a data source to be functional.

The following objects are static objects and cannot be bound to an attribute:

The following objects are optionally dynamic and might be bound to an attribute, but are not required to be:

These optional dynamic objects when bound to an attribute cause the attribute to be of the type Usage Inquiry. This enables an attribute value to be displayed on the screen, but not receive input from the screen or write to the database. Usage Inquiry is only used to display data values on the screen.

Usage Inquiry Attributes can be receiving fields only. They might not be used as source fields for arithmetic or data manipulation in Logic.

An example where an image could be bound to a Usage Inquiry attribute is where you might want to change the image displayed on a form depending on a previous input action of a form, say a warning sign appears if an error occurred in an input transaction.

The relationship between dynamic graphical objects and an attribute exists to enable the user to interact with the attribute so that records in the underlying database can be read, created, modified, and deleted by the user (where applicable). The interaction is carried out by the user manipulating the objects on the form with the actions permitted by a given object, for instance, a Button can be "clicked" and an item in a List box can be selected.

Special consideration needs to be made for the GridPanel functionality when populated with Radio Button, checkbox, or Button objects.