Takes two parameters, the variable name and a value
Takes a variable number of parameters
Takes a variable number of parameters
Takes a variable number of conditional statements to compare against a single source
Takes a variable number of parameters.
Takes a variable number of conditional logical if statements
Takes one parameter bNoHeaders and returns the result to an assigned variable
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 variable number of parameters
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
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 four parameters, Source, bAny, Search, Item
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.
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.
This style guide provides comprehensive standards for writing clean, maintainable, and consistent MOX code for Moxie.Build. Code examples on this page are for illustrative purposes and are only intended to demonstrate style conventions.
The MOX coding and programming 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, 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.
Parameter is a comma separated list (using CSV rules and not in quotes) of the fixed hard coded values to select from
Takes one parameter.
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.