Changes the name of certain objects.
Syntax
RENAME object oldname AS newname [IN directory]
Parameters
| object | One of
CONSTANT, DIRECTORY, DISPLAY, DOCUMENT, ENTITYSET, FORM, RELATIONSHIP, ROLE, SET, VARIABLE, WINDOW |
| oldname | The current name of object. |
| newname | The new name for object. The new name must not be the name of an existing object. |
| directory | The name of the application directory in which object is located. |
Example
rename entityset Deppartments as Departments
The preceding command renames an EntitySet that was accidentally given a misspelled name.
See Also
CREATE
ERASE
How To Name Objects
Specifies the vertical heading for each page in a column-oriented report.
Syntax
PAGE LEFT reportitem [:format:]
Parameters
| reportitem | Any valid expression. Complex expressions must be enclosed in parentheses. When you specify more than one expression, each must be separated from the next by at least one space. |
| format | A set of instructions defining the format for the associated reportitem. Format is enclosed in : (colons) and can consist of any valid combination of format options. |
Comments
The PAGE LEFT command generates a “heading” along the left-hand edge of each page in a column-oriented report. The column of text generated by this command starts in column 1 on the page. Report items in this command can include individual data values only from the first record to be processed on the current report page.
See Also
How to Use The Report Generator
Output Masks
Report Item Format Options
Starts an explicit transaction.
Syntax
TRANSACTION [READ]
Parameters
| READ | This option is ignored. |
Comments
TRANSACTION marks the start of a sequence of commands that are to be handled as a single transaction. The transaction can be terminated either with an ENDTRANSACTION or with a QUITTRANSACTION command.
TRANSACTION sets the system variable $InTransaction to $True.
Example
form set accelerator Return Escape
while
form open fEmpForm
form display input
if Event.EventName <> “Escape”
find Departments where Departments.Dno=fEmpForm.Dno
if $setcount = 0
form open fDeptForm
form display input
endif
transaction
if $setcount = 0
add Departments from fDeptForm
endif
add Employees from fEmpForm
endtransaction
else
return
endif
endwhile
See Also
BEGIN WORK
ON
QUITTRANSACTION
SET TRANSACTION FLOW
Generates application code from a template.
Syntax
GENERATE zimprog [ (parm)|string ]
Parameters
| zimprog | The name of an application document that contains an application program template. |
| parm | An expression whose value is to be passed to zimprog. Multiple parameters must be separated from one another by commas. |
| string | A string that is passed to zimprog if zimprog is a macro program. |
Comments
The commands in zimprog are executed interactively. When an opening program template delimiter (<<) is encountered, execution is suspended, and the subsequent lines are written (after macro substitutions) to the current output. This process ends when a closing program template delimiter (>>) is encountered alone on a line.
See Also
$ (Template line join)
Program Templates and the GENERATE Command
Branches from an exception handler to the command that caused the exception.
Syntax
GOTO PREVIOUS
Comments
GOTO PREVIOUS is used only in an exception handler and only to branch to the command that caused the exception to occur. GOTO PREVIOUS exits the exception handler, and closes it in the same way as ENDON.
Example
Note: In this example, all transactions are assumed to be implicit transactions (i.e., single commands).
procedure UpdateDB()
on deadlock
output “The database is busy.”
output “Do you want to try again? ( y/ n):” ;
input Response
if Response = ” y”
goto previous
else
return
endif
endon
… the rest of the commands in the procedure …
endprocedure
If a deadlock condition occurs, the exception handler asks the application user if the transaction should be attempted again. If the answer is yes, the GOTO PREVIOUS command causes the application program to retry the command that caused the deadlock condition. If the answer is no, the procedure terminates.
See Also
GOTO
GOTO NEXT
ON
Specifies the page footing for a report.
Syntax
PAGE FOOTING reportitem [:format:]
Parameters
| reportitem | Any valid expression. Complex expressions must be enclosed in parentheses. When you specify more than one expression, each must be separated from the next by at least one space. |
| format | A set of instructions defining the format for the associated reportitem. Format is enclosed in : (colons) and can consist of any valid combination of format options. |
Comments
the PAGE FOOTING command causes a footing to be displayed at the bottom of every page of a report. Report items in this command can include individual data values only from the last record processed on the current report page; however, summary information computed over all the members on the current report page can be displayed in the footing.
See Also
BREAK (Reports)
How to Use The Report Generator
PAGE HEADING
REPORT FOOTING
Report Item Format Options
Sorts the members of an existing result set.
Syntax
SORT [setname>] BY expression [ASCENDING|DESCENDING]
Parameters
| setname | The name of a result set. If setname is not specified, the current set is used. |
| expression | An expression that identifies a field to be used as a sort key. Complex expressions must be enclosed in parentheses. |
| ASCENDING or DESCENDING | Specifies how the sort on the associated key is to be performed.
ASCENDING (default)
Sorts in “alphabetical order” (A-Z, 0-9).
DESCENDING
Sorts in “reverse alphabetical order” (Z-A, 9-0). |
Example
find all Employees where Name = Smith -> SmithNames
sort SmithNames by Salary
The preceding two commands could be combined into one by using a SORTED BY subcommand.
sort SmithNames by FirstName DeptNum Salary descending
The preceding command sorts the employees named Smith by first name (ascending order), department (ascending order), and salary (descending order).
See Also
SORTED BY
Specifies the vertical footing for each page in a column-oriented report.
Syntax
PAGE RIGHT reportitem [:format:]
Parameters
| reportitem | Any valid expression. Complex expressions must be enclosed in parentheses. When you specify more than one expression, each must be separated from the next by at least one space. |
| format | A set of instructions defining the format for the associated reportitem. Format is enclosed in : (colons) and can consist of any valid combination of format options. |
Comments
The PAGE RIGHT “footing” is placed along the right-hand edge of each page in a column-oriented report. The column of text generated by this command ends in the right-most column of the page. Report items in this command can include individual data values only from the last record processed on the current report page; however, summary information computed over all the members on the current report page (using aggregate functions) can be displayed in the footing.
See Also
How to Use The Report Generator
Output Masks
Report Item Format Options
Deletes data from EntitySets or relationships with fields.
Syntax
DELETE [num] [setspec] [EVALUATE clause] [-> clause]
Parameters
| num | Can be
an integer constant (15, 200);
a variable, a form field, or a parameter that evaluates to an integer;
the word ALL.
If num is omitted, or less than 0, it defaults to 1. |
| setspec | The set specification for the simple set whose records you want to delete. If omitted, records are deleted from the current set (if it exists). |
Comments
Records cannot be deleted from a composite set. Data cannot be deleted from application documents or forms.
If the target of DELETE is a set object or result set, deletion always starts at the current member of the set.
Data removed from the database by a DELETE command cannot be recovered.
Example
delete
Deletes the current member of the current set.
delete 5 Employees where DeptNum = D01
Deletes the first five records in Employees where the department number is D01.
See Also
$MemberCount
DELETE FROM
Encrypts the data in an EntitySet or relationship with fields.
Syntax
ENCRYPT object
Parameters
| object | The name of an EntitySet or a relationship with fields. Can be a role name. |
Comments
The ENCRYPT command makes stored data meaningless to anyone scanning a raw database file on disk, thereby protecting the data from unauthorized access. The encryption key is established when the New Database utility is executed.
If the data in the specified object has already been encrypted, reissuing the command raises an error.
The ENCRYPT and DECRYPT commands prevent users outside of an application session from reading sensitive data contained in disk files. All encryption and decryption in a particular database is based on a key established when you initiate a new database .
Encrypted EntitySets and relationships are accessed in exactly the same way as un-encrypted EntitySets or relationships. Internally, the software automatically decrypts data from an encrypted file as you work with that file. A slight performance penalty is paid for working with encrypted data.
An encrypted object can be returned to normal with a DECRYPT command.
See Also
DECRYPT
Securing Data Inside an Application
English 
Portuguese