•Each table in this documentation includes all of the attributes available in Object Navigator for the corresponding object. This includes relationships that do not exist in the database.

•Attributes are listed in alphabetical order within each table.

•You can use the grouping of tables in the left pane to understand the relationships between the various tables. The tables are grouped in the left pane according to the main objects to which they are most closely associated (such as Account, Project, or Task). Tables that are administrative and are not closely associated with one particular object are listed in the Common section.

•Each main object's tables are listed in the following order:

a.T-table

b.J-tables and their corresponding R-tables

c.Category and Custom Field tables (E-tables)

d.User and group access tables

•Object (table) names are provided as links, so that if you are viewing this documentation electronically, you can quickly navigate to the table for the corresponding object.

•Items that have the data type object are treated as objects, rather than foreign keys (as they are treated in the database) in the descriptions that are listed in the Comments column of each table. This is why the Comments column does not indicate that an attribute stores the ID or primary key of the object, but instead indicates that the attribute identifies the object itself. This convention is followed in order to lessen confusion for users who are not concerned with the way the database actually works.

For example, in the table TInvolved, the attribute project--> is described as the project to which the involved record belongs, rather than the primary key of the project to which the involved record belongs.