If an index entry appears in multiple table columns, then it is a composite index. A composite index requires multiple columns in order to create a unique index.
Added in Version 6.0
The SECCODEJOINS table stores the field-level security information linking users to teams to security profiles. As an example record, the ChildSeccodeID could contain the SeccodeID for Cathy Hughes, the ParentSeccodeID could contain the SeccodeID for the team (Northwest), and the ProfileID could contain the ProfileID for the Team Owner Profile. This information is entered in the Administrator (user profile > Teams tab).
|
|
If an index entry appears in multiple table columns, then it is a composite index. A composite index requires multiple columns in order to create a unique index. |
| Field | Datatype (Length) | Allow Nulls | Indexes | Relationship | Related Table and Field |
|---|---|---|---|---|---|
|
PARENTSECCODEID (PK) (FK) |
char(12) |
NOT NULL |
SECCODEJOINS_COMPOSITE_PK (CA) |
(Many) to (One) |
|
|
PROFILEID (FK) |
char(12) |
NULLS |
SECCODEJOINS_PROFILEID (IE) |
(Many) to (One) |
|
|
MODIFYDATE |
datetime(8) |
NULLS |
|
|
|
|
MODIFYUSER (FK) |
char(12) |
NULLS |
|
(Many) to (One) |
|
|
CREATEDATE |
datetime(8) |
NULLS |
|
|
|
|
CREATEUSER (FK) |
char(12) |
NULLS |
|
(Many) to (One) |