Like a real tree, your database of information is organized along major "Branches" below the "Root". Within each "Branch", you can further separate your notes into additional "Limbs", "Twigs", "Leaves", etc. This ability to continue the level by level breakout is what makes the "Tree" structure such a powerful facility for information organization.

The single value fields can be configured to contain data of the following types: 1. Text, 2. Date, 3. Numeric, 4. Currency.

Note Properties ... Each note placed on the Tree has a set of properties, some of which, by default, are inherited from it's parent. The user can, however, override and/or change any of these properties to better suit their information storage requirements.

Each note has the following properties:

Let's consider how these note properties can affect your creation of new notes within your "Tree" structured database.

When a database is first created, there is a single note that is referred to as the "Root" of the "Tree". This "Root" note, by default, has the following properties:

Thus, by default, all notes that are added below this "Root" will be designated as Sorted, Standard Display Image, User Fields Visible.

Before you start placing additional notes on your "Tree" you should review the properties of the "Root" note and adjust any of them that will better serve your needs, remembering the rules of inheritance.

Let's review a few scenarios:

Scenario 1 ... mostly free-form information and notes are to be sorted by title.

Since most of the notes will not take advantage of User Definable Fields, let's start by setting the "User Fields Visible" property of the "Root" so that it's User Fields do not show. Thus, as we create notes below the "Root", they will inherit this property. Then for specific notes for which you want to use the User Definable Fields, you simply set this property so that they will show.

By default, the "Root" has it's Sorted property set to "yes", so all notes added below it will also have their child notes arranged alphabetically by note title.

Scenario 2 ... mostly free-form information and note placement is to be user controlled.

This would be the same as scenario 1 as it relates to User Definable Fields; however, since the user plans to control the placement of the notes, we should go to the "Root" and turn off its Sorted property.

Scenario 3 ... User Fields to be used frequently but the formats vary.

Since most of the notes will take advantage of User Definable Fields, let's start by setting the "User Fields Visible" property of the "Root" so that it's User Fields do show. Thus, as we create notes below the "Root", they will inherit this property.

Each major branch of your database "tree" may required different formatting of the User Definable Fields. For example, one branch may be for storing information about PC workstations within a LAN while another branch may be for storing information about product testing results. So ... as you begin to add specific branches to the tree, you will want to configure their use of the User Definable Fields to suit your information storage formatting needs. One branch may use several text fields, a couple of date fields, etc. Another branch may use mostly date and currency fields.

By configuring the top of each branch for your formatting needs, the notes created below each branch will have their User Definable Fields configured by default through inheriting properties from their parents.