Click above to get retro games delivered to your door ever month!

   The program generated for a Form object is organised in the following way:

     . All associated files are opened, and the instance variables
       initialised.

     . The current record is verified against the eventual pending
       filter conditions. If the record does not match the criteria, the
       first matching record is seeked.

     . The general parameters of the object are verified (with the
       tbConfig() function)

     . The form is displayed and the memory variables for holding
       the data of the fields are created.

     . The inkey handler is called. The inkey handler will wait for
       any key press, mouse movement and selection, or other event to occur.

     . The inkey handler traps any record modification request.

     . During modification, the (static) memory variables are
       initialised with the contents of the current record's fields.

     . During insertion, the file associated is in a end-of-file
       situation, and the memory variables are initialised to an empty value.

     . After the edit, all consistency and unique controls are
       performed on the data, the variable are written to disk, and the inkey
       handler returns in consultation (idle) mode.

     . When exiting the inkey loop, all files opened are closed,
       and the screen area occupied is restored to the previous state.

   The interaction between the user of the generated application and the Form
   object defined, is realised by a set of functionalities associated to the
   controls inserted in the object. For example, executing checks on the data
   associated to each control before being displayed and after being
   modified.