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

   The Design operations made on a Query object are similar to those made on
   the Form object, with the difference that, for each reference to the
   fields of the database, a search condition is asked for. This condition
   acts as a filter on the data to print. The conditions available are:

     . I<-->I range (with boundaries)

     . <--> range (without boundaries)

     . < less than

     . > greater than

     . <= less than or equal to

     . >= greater than or equal to

     . = equal to

     . # not equal to

     . $ contains

     . C is contained in

     . ==exactly equal

Example:

   On the Query, a Get control relative to the invoice code (CodInv)
   field of the invoice header (InvHd) is created, and associated to the
   search condition "greater than". If, in the generated application, the
   user inserts a value of "40" in this control, only those virtual records
   that have a value in the CodInv field greater than 40 will be printed.

   It is up to the project designer to make the user understand the meaning
   of the values that are inserted. In the previous case, for example, it is
   advised to substitute the description of the CodInv field with the
   text "From invoice code".

   In a Query object, the logical AND and OR connectors are used to
   link the query expression of all controls together. The insertion of a
   logical connector is automatically given as an option after each query
   expression is inserted, except the for first condition set.