MultiValue Compatibility
Certain DataBasic program elements can have different functionality, depending on the compatibility mode set using $OPTIONS statement. This section describes these elements, the effects of different compatibility settings and lists the default settings for the different compatibility modes.
It also describes functionality that is provided only for compatibility with other MultiValue systems.
Runtime behaviour of a DataBasic program
The runtime behaviour of a DataBasic program or subroutine is determined by a combination of two factors:
-
The run-time version embedded in the compiled code. This normally depends on the compiler used, but can be changed with the $OPTIONS statement.
-
The MultiValue compatibility mode (if any) set with $OPTIONS statement.
Note
The topic Compatibility Switch Matrix describes the different compatibility settings and lists the default settings for the different compatibility modes.
Features that depend on the compatibility mode
-
@ function
-
DELETE statement
-
DELETESEQ statement
-
DQUOTE function
-
OPENSEQ statement
-
READLIST statement
-
REMOVE statement
-
SELECT statement
-
SQUOTE function
-
SYSTEM function
-
WRITE statements
Reality features with additional functionality
-
EQUATE statement
-
FIELD function
-
GROUP function
-
MATPARSE statement
-
READNEXT statement
-
READPREV statement
Additional features
-
@DAY, @MONTH and @YEAR predefined symbols (MVENTERPRISE compatibility)
-
Boolean Compiler Directives (MVENTERPRISE compatibility)
-
ASSIGNED function
-
CHANGE statement
-
CLEARINPUT statement (MVENTERPRISE compatibility)
-
DISPLAY statement (AP, D3, MVBASE, PICK and R83 compatibility)
-
CREATE statement
-
EREPLACE function
-
EXECUTE statement
-
FORMLIST statement (MVENTERPRISE compatibility)
-
MSLEEP statement
-
OUT statement
-
QUOTE function
-
STATUS function
-
SWAP function
-
TCLREAD statement (D3 compatibility)
-
TRANS/XLATE function