Use the Eclipse Dictionary to define and access the information stored in data files. Every data file has a corresponding dictionary file. The dictionary file contains one or more dictionary items for each field in the file. Dictionary items translate data file information so you can easily view and understand it. The system stores the file data in an internal form, which is more efficient for processing the data, and uses dictionary items to display the data in an external form, which you can understand.
The system uses dictionary items when loading information into a file from the mass load program or data entered on a screen, or when extracting information from the file to display on a screen or print on a report. The system uses a relational database to store information. When you design a report or mass load, you identify the data in the file using dictionary IDs. You must have a good understanding of the Eclipse Dictionary in order to use the Report Writer/Mass Load programs.
To understand the difference between data files and dictionary files, remember:
Data files hold records.
Dictionary files are instructions and rules that apply to the data files.
The system stores its information in a relational database. Data is easier to access and process when stored in the following way:
Data is separated and stored in files. For example, the Customer file contains details about the customers to whom you sell products.
Each file contains records. For example, the Customer file contains a record for each customer.
Each record contains fields of information called attributes. Within each record the same type of information is stored in the same attribute. For example, as shown in the following table, attribute 1 stores the customer phone number and attribute 4 stores the accepted payment types from the customer.
Attributes can be multi-valued. In the following example, for customer Long, the payment type values are Credit Card and Check.
A multi-value can have sub-values. In the following example, for customer Long, Visa and MC are the sub-values for the Credit Card value.
A unique key identifies every record to the system. The key is a number, which the system assigns when you create the record. The system stores the key in attribute number 0 (zero).
Customer File Example:
|
Record |
Attr 0 Item ID |
Attr 1 Phone # |
Attr 2 First Name |
Attr 3 Last Name |
Attr 4 Payment Type |
|
1 |
001 |
303-444-4444 |
Susan |
Long |
Value: Credit Card Sub-value: Visa Sub-value: MC Value: Check |
|
2 |
002 |
303-555-5554 |
Billy |
Wilson |
Value: Credit Card Sub-value: MC |
|
3 |
003 |
303-666-6666 |
Richard |
Short |
Value: Check Sub-value: |
Every data file has a corresponding dictionary file. The following information applies to items in the dictionary file:
Each dictionary item identifies data in a file by name rather than attribute number.
For example, attribute 1 in the previous table contains the customer phone number. The dictionary ID and description for this attribute can be Cust# and Customer Number.
Dictionary items for numerical data define a display format.
For example, dates are stored in the database as numbers. You can use dictionary item definitions to display dates in different formats, such as September 15, 1997, 15 Sept 1997, or 09/15/97.
You can define multiple dictionary items for a single attribute.
For example, using the date in the previous example, you can set up each display type as a separate dictionary item. One dictionary item displays the date in the 15 SEP 1997 format and another dictionary item displays the date in the 09/15/97 format.
You can create a dictionary item for each value in a multi-valued or sub-valued attribute.
There are two types of dictionary items:
D-type dictionary items define physical fields of data, such as the Name field in an entity record.
I-Descriptor dictionary items create new values by manipulating data from files.
See Also:
Viewing Dictionary Items Defined for Files