Changing a Maintenance Dialog

Use

There are two possible reasons for changing an existing maintenance dialog:

For technical reasons, for example, table or view changes (addition or deletion of fields).
For application reasons, for example, additional input data consistency check logic required. Types of changes:
- Maintenance screens (layout and flow logic)
- User Interface
- Events in program flow

User program code can only be included via user includes. The includes must be created manually in the function group.

Dialog changes must be made such that regeneration does not lose modifications. You can use the Generate Table Maintenance Dialog tool to regenerate selectively, that is, to replace only the necessary dialog components. If you have changed maintenance screens, the interface or the main program, you should exclude them from the regeneration. Maintenance does not affect events.

Process

Maintenance

You can control the maintenance dialog change types with the Generate Table Maintenance Dialog tool:

Change maintenance type

Change the maintenance type from one-step to two-step or vice versa.
Create module
Create maintenance screen

Reset generated modules or maintenance screens to default values.
Field/sec. table in structure
Remove field/sec. table from structure

Adjust maintenance dialog when Dictionary structures have changed. Only for views.
Change text table link

Adjust maintenance dialog if you have assigned a table to another text table in the Dictionary. Only for tables.

Note
A text table is automatically included in the maintenance dialog if a Text Table Key Fields foreign key relationship is assigned in the Dictionary for the table.
Changed selection conditions
Field attribute subset changed
Field attribute read-only changed
Field attribute hidden changed

Adjust maintenance dialog when Dictionary selection conditions or field attributes have changed.