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

   Notice that the Lookup control does only display the data belonging to the
   related file, and does not allow any edit to be performed directly.

   When the information associated to a Lookup control must be displayed, the
   system operates in the following way: the data (i.e. the field on which
   the relation is created - usually a code) is taken from the main file and
   is seeked in the related file. If it is found, the information contained
   in the related file is displayed. The main file will only store the seeked
   value (code), and the associated information is kept in the related file.
   This mechanism makes the database more efficient, because recursive
   information is coded uniquely and stored once in the related file,
   avoiding redundant data.

   During desing, the Lookup is identified by a ">" character put in
   front of the control.

Example:

   When designing a Clients data management system, some of the records may
   indicate the same postal (zip) code thus the same city. If the database
   has been designed to reserve two fields for both the postal code and the
   city, many records with the same postal code will also have the same name
   stored. This would create redundant information (the postal code is
   sufficient). If the city name is extracted from a related file using the
   postal code, both information is available while using only one field.