Child pages
  • Inheritance Model

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


When using form inheritance, the properties and methods can still be overwritten in the sub forms. This is not the case for the datasource, the datasource can not be changed from one table to another, it can be changed from empty to a table.




of Inheritance

Form 'code_base': Here are all the functions like 'new record', 'delete record' ect. On this form there are no parts, it is strictly code. This form will have no datasource.
Form 'data_controller': Here are buttons for the actions 'new record' and 'delete record' ect. There could be more than one, so there can be multiple designs. This form will inherit the 'code_base' form and uses all it's functions. This form will have no datasource.
Form 'customers': This will inherit the 'data_controller' because the functions and buttons are already inherited only the datasource and fields have to be added and there is a working form.



a Super Form

On an existing form, the super form can be set by going to the properties and setting the "extends" property to the super form.


There are not many limitations to form inheritance. One of the limitations is that if there is an element on the super form, it can not be deleted on the sub form, if it should not show on the sub form the visible property of the element can be unchecked. Another limitation is that there cannot be new parts added in-between existing ones, new parts can only be added below existing parts.



and Security

The security of a form that is extended works like it would work if it was not extended, security can be set on all the elements on the form, even if they are inherited. The security has to be set on the form that the user uses and not on one of the super forms. In the security tab it is shown from what form the inherited elements are inherited.