Takes two parameters, the variable name and a value
Takes a variable number of parameters
Takes one parameter, a top query destination variable
Takes one parameter bNoHeaders and returns the result to an assigned variable
Takes a variable number of parameters.
Takes a variable number of parameters
Takes a variable number of parameters
Takes a variable number of parameters
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes a single variable, the relative path to the directory from root of project
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc..]
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc...]
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes a variable number of conditional statements
Table Actions are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As an Action, the Procedure is expected to perform some sort of task, such as an automated set of updates to the Database Table.
Record Actions are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As an Action, the Procedure is expected to perform some sort of task, such as an automated set of updates to the Database Record.
Has no parameters.
This hands-on experience article is written by an experienced PHP developer, and serves as an overview to help you understand the similarities and differences.
The MOX language pays heritage to BASIC, but has been crafted for the specific type of work and environment that is demanded of Moxie.Build.
Takes one parameter.
Takes one parameter, FieldBase
Table Reports are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As a Report, the Procedure is expected to produce output to be displayed to the user.
Record Reports are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As a Report, the Procedure is expected to produce output to be displayed to the user.
Takes four parameters, Source, bAny, Search, Item