$OPTIONS Statement
Sets the compatibility mode for the current code module. This changes the functionality of various DataBasic statements and functions to match that of the selected MultiValue system. Refer to MultiValue Compatibility for details.
Syntax
$OPTIONS {system}
Syntax Elements
system One of the following keywords, representing the required MultiValue system:
Value |
MultiValue System |
---|---|
REALITY |
Reality |
EXT |
Reality (extended) |
AP |
Advanced Pick |
D3 |
D3 |
GA |
GA Pick |
IN2 |
Intertechnique |
INFORMATION |
Prime Information |
MVBASE |
mvBase |
MVENTERPRISE |
mvEnterprise |
PICK |
R83 |
PWR95 |
Power 95 |
R83 |
R83 |
UNIVERSE |
UniVerse |
UNIVISION |
UniVision |
UNIDATA |
UniData |
If system is omitted or no $OPTIONS system statement is present in the module, DataBasic operates in REALITY mode.
Comments
Only a single MultiValue system can be selected. However, additional $OPTIONS statements can be used to select compiler options.
Unless used in an automatically included module, the effect of a $OPTIONS statement is local to the module in which it appears. If used in a subroutine, any previous $OPTIONS settings are restored on return to the calling module.
When you select one of the above MultiValue compatibility modes, an appropriate symbol is defined, as follows:
Compatibility Mode |
Symbol |
---|---|
REALITY |
$REALITY * |
PICK |
$PICK |
GA |
$GA |
INFORMATION |
$PRIME |
IN2 |
$IN2 |
MVBASE |
$MVBASE |
MVENTERPRISE |
$MVENTERPRISE |
UNIVERSE |
$UNIVERSE |
UNIVISION |
$UNIVISION |
UNIDATA |
$UNIDATA |
These symbols can be used to control condition compilation with the $IFDEF and $IFNDEF statements. They can all be undefined if required with the $UNDEFINE statement.
* The $REALITY symbol is always defined. It is not undefined if you select a different compatibility mode.