Prefix

Description

Examples

T

T-tables are the 11 main tables for TeamConnect objects. In Object Navigator, they are almost always the starting point of navigation.

A T-table contains the basic information for each record of its type that is created. In other words, it contains instances of an object definition. T-tables own specific instances of custom fields (E-tables), categories (E-tables), and sub-objects (J-tables), all of which store items added to the record in batch screens.

T-tables are not owned by any other kind of table. However, a T-table might have a relationship to another T-table. For example, T-History is related to all of the other T-tables, because History records can be created for each kind of record.

•TAccount

•TAppointment

•TContact

•TDocument

•TExpense

•THistory

•TInvoice

•TInvolved

•TProject

•TTask

J

J-tables are owned by T-tables (or, occasionally, R-tables). J-tables are also known as sub-objects.

The values stored in J-tables are usually obtained from lookup tables (L-tables). In the UI, items in a J-table are added to a record through a batch screen. For example, assignees added to a project in a batch screen are sub-objects of the project.

•JApptAttendee

•JContAddress

•JContEmail

•JProjAssignee

•JTranDetail

L

L-tables store the main lookup table information for system lookup tables.

•LContFaxType

•LCountryItem

•LProjAssigneeType

•LContSkillType

E

E-tables are used with every T-table throughout the object model to store the following:

•specific categories that have been added to records

•specific custom field values added to records

•specific user or group security settings for records

•EHistDetail

(contains categories that have been added to History records)

•EHistDetailNumbValue

(contains values that have been added in custom fields of the type Number, in History records)

•EHistUserAccess

(contains user security settings for History records)

R

There are only four R-tables in the object model. Each of the R-tables has a unique purpose (shown at right).

Like T-tables, R-tables are not owned by any other table. However, they do not contain all of the attributes found in a T-table. For example, they do not have custom fields or categories associated with them, and they do not belong to an object definition.

•RTransaction

(stores instances of financial transactions)

•RDistribution

(stores contact groups, that is, Address Books)

•RApproval

(stores instances of approvals)

•RForum

(stores any forums created for records)

Y*

Y-tables are system tables. They typically contain values that correspond to administration objects, such as groups and users. They are owned by Z-tables.

Custom lookup table information is also stored in Y-tables.

•YGroup

•YUser

•YDetailLookupTable

•YDetailLookupItem

W*

W-tables store object definition information. The components related to object definition are stored in these tables. They are owned by Z-tables.

Categories and custom field definitions for all objects are also stored in W-tables.

•WObjdCategory

•WObjdDetailField

Z*

Z-tables own W-tables and Y-tables. They contain specific information pertaining to system design, such as object, template, wizard, and search view definition information.

ZObjectDefinition

U*

U-tables are administrative tables that are owned by W-tables.

UGrupMember

* Most tables that are named with this prefix are not typically used when creating rules, templates, wizards, or object naming patterns, although there are certain exceptions. For example, UGrupMember is used in rules that check whether the current user is a member of a certain group.