I also want to name the possible problems with the use of the program. It is not about mistake in the real sense special more around difficulties which are not to be solved yet.
With the Aggregation, Subtypes and foreign-key only one-attribute-primary-key per object are supported. An object is identified only by one attribute.
With empty tables the insertion of the first Tupels is possible only with the command buttons save (diskettes-icon).
The data in a form are sent only after the change the Tupple-position (with navigation buttons) or by the command button save.
There are problems with operations (Delete, Change, Create), they become only a visible after the action reload. The condition that the data will not could be current by the red-colored command button reload indicated.
The number of open SQL-connections is limited system-specifically. With MySQL can be opened up to 10 forms at the moment
Only once the Widget (Multi-Column-Listbox) for the announcement of foreign key are initialized while opening the form. If the condition of the objects should change at which the foreign keys point, it is not indicated.
The forms which can be used with Aggregation separately are opened, however, the foreign keys are indicated as a normal Widget. This can manually inFormEditor Are changed, however, it is not shown by form assistants automatic.
Form-links functioning if one does not point at the root-form, the foreign key, however, in a children's form is. See Tutorial (form Professor link on assistant). Such FormulaLinks need a special treatment which was not programmed yet.