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 =…
Read more
The name assigned to a role. Valid Values An 18-character string, containing a valid object name See Also ConstName, DDObjectName, DDOwnerName, DirName, DisplayName, DocName, EntName, FieldName, FormName, MenuName, OwnerName, RelName, SetName, UserName, VarName
The members of the owner-object associated with the role. An expression that indicates which members of the owner-object are represented by a role. Valid Values Any conditional expression involving fields from the owner-object only. If the role condition is omitted, the associated role name applies to all members of the owner-object. Remarks For example, a…
Read more
A user-assigned numeric identifier. Valid Values An integer in the range 0 to 255 Remarks Several UserNames may share the same UserId. Only a “super user” (i.e., a user whose GroupId is 0) can view or update the Users entity set. See Also GroupId, UserName
A user-assigned numeric identifier. Valid Values An integer in the range 0 to 255 Remarks Several UserIds may share the same GroupId. Only a “super user” (i.e., a user whose GroupId is 0) can view or update the Users entity set. See Also UserId, UserName
The number of elements in a variable. Gives the size of array variables. Valid Values Any integer (DEFAULT = 1) Remarks If Size is 0 or 1, the variable is scalar and has one element. If Size is greater than 1, the variable is an array, with Size elements.
The name assigned to a variable. Valid Values An 18-character string, containing a valid object name See Also ConstName, DDObjectName, DDOwnerName, DirName, DisplayName, DocName, EntName, FieldName, FormName, MenuName, OwnerName, RelName, RoleName, SetName, UserName
Despite thorough testing, an application can experience operational problems. These problems can result from faulty coding or they can be environmental in origin (e.g., stemming from the interaction of the application and the operating system). In either case, the approach to troubleshooting an application uses the same three-step process: 1. Reproducing the Situation A fundamental…
Read more
English 
Portuguese