Category: Relationships (Rels)

The name of the owner of the database table on the database server if the table is not owned by the user or included in his or her schema.

Remarks

The name of the owner of the database table on the database server

The name of the database table on the database server, if different than the EntitySet name. RemoteName is normally used when there is a naming incompatibility between Zim and the database server.

Remarks

The name of the database table on the database server

Whether this relationship is defined to be per user.

Valid Values

“yes” or “no” (the default value is “no”).

Remarks

The RelPerUser field only applies to Relationships with fields because there is no physical file to be handled.

Normally, Relationships with fields belong to the database and are managed by ZimServer. However, per user Relationships have these differences:

. They are handled by the current session and their information is lost after the session finishes;

. They are located in the $WorkPath directory;

. They don’t suffer any locks because they belong to the current user and no other users can access them;

. They don’t exist at the beginning of the session and must explicitly be created (or recreated) at any time by the application via the command INITIALIZE PERUSER. There is no need to keep a “storage” full of empty copies of all per user Relationships used by the Zim  application.

In previous versions of Zim, per user Relationships were indicated with the “)” mark in the AREAS.ZIM file. This is no longer needed and any such entries will flagged with an error.

The name of an application directory (Directories); otherwise, the one application directory in which the associated object may exist.

Valid Values

An 18-character string, containing a valid object name

Remarks

In Directories:

DirName is the name assigned to the directory.

In other Object Dictionary entity sets:

In any entity set, the principal object’s DirName must match the DirName of its owner.

If DirName is left blank, the object may exist in any number of application directories.

In DDDescriptions, DirName is where the object being described may be found.

In DisplayForms, DirName is where the owner-display of the associated form may be found.

See Also

ConstName, DDObjectName, DDOwnerName, DisplayName, DocName, EntName, FieldName, FormName, MenuName, OwnerName, RelName, RoleName, SetName, UserName, VarName

A user-assigned classification for a relationship.

Valid Values

A character string, up to 18 alphanumeric characters

The name assigned to a relationship.

Valid Values

An 18-character string, containing a valid object name

See Also

ConstName, DDObjectName, DDOwnerName, DirName, DisplayName, DocName, EntName, FieldName, FormName, MenuName, OwnerName, RoleName, SetName, UserName, VarName

The number of records in the database object. An estimate of the number of records in an entity set, named set, relationship with fields or an estimate of the number of records (lines) in a document.

Valid Values

A non-negative number (vastint)

If you enter 0 or leave the field blank, an internal default value is used.

Remarks

AvgSize is used by the strategy analyzer to determine the most efficient access strategy when a database object is used in a set specification. AvgSize does not restrict the physical size of the object in any way.

A unique identifier assigned by the Development Center.

Valid Values

A 25-character string (DEFAULT = $Null)

Remarks

ObjectKey is a unique identifier assigned by the Zim Development Center if the Object Manager (ZOM) has been enabled. End-users should not modify its value. Refer to the Development Center documentation for more information.

ObjectKey has a defined ListWidth of -1 and is not normally displayed.

The conditional expression that defines a relationship. The specific association between objects.

Valid Values

Any conditional expression

Remarks

Objects mentioned in the RelCondition should exist before the relationship is created. Referenced objects that do not exist when a RelCondition is created are interpreted as character strings if SET QUOTING is OFF.

For example,

Employees.DeptNum = Departments.DeptNum

defines a relationship between employees (in entity set Employees) and their departments (in entity set Departments) using a common department number (DeptNum).