Writing applications often requires creating a lot of small forms, especially for mobile
apps. To make app management easier, consider creating a common form that has all operations
generated for it, then limiting the operations as it is opened in different scenarios in the
app.
There are several ways to reuse a form in an application. For an example of setting many
relations to a common form, see
Example: Single CRUD forms or Common CRUD form.
- Use it as is
- In the BA diagram, set a relation to the form as is.
- Reuse a subset of functionality
- Create the form will all CRUD operations generated. Then, in the BA diagram relation to the
form, set the properties to disable Add, disable
Modify, disable Delete, and/or disable
Search. When the form is opened, only a subset of the operations will be available to
the user.
- Display a subset of the data depending on the parent form
- The Filter properties on a relation are
used to apply a SQL filter to show a subset of data when opening a form. See Opening a form with a subset of data
- Position the cursor depending on the parent form
- When a form is opened from another form, the current position
is always set to the first row. With positioning, you can control the row that is preselected when
the form is opened. The Position, Source Field property on the relation to the form
controls which row will be displayed when the form is opened. See Control the row position in form.