Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- dBsee 4.6 - The Library - Norton Guide http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]

   A File A is in a 1:N relation with a file B if for each record in
   file A it is possible to identify one or more records in file B.

   For example, each invoice has many elements (Invoice Detail Rows), but
   each element refers to only one invoice. The invoice represents the term
   One, the detail rows the term Many.

   Another example is a company that has many employees, but each employee
   has only one company that he/she works for. The company is the One and the
   employees are the Many.

   To define a 1:N relation it is necessary to enter the following
   parameters:

     . Parent File (1)

     . Child File (N)

     . Relation Index on the child file

   The relation index allows the system to quickly finding the first
   record of the child file corresponding to the current record of the parent
   file. With these parameters, the system will automatically define the
   criteria for the 1:N relation. These criteria are:

     . Primary positioning key

     . Filter condition

     . Break condition

   A group of options that influence the behaviour of the generated
   application can also be defined for each 1:N relation. For this type of
   relation, it will be possible to:

     . establish the referential integrity rule choosing from 5
       types: Restrict, Nullify, Cascade, Orphan and
       Prevent;

     . modify the primary positioning key within the Lookup file;

     . define keys, filters and breaks parameters.

   These options are examined in the following paragraphs.

Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson