Parameter is divided into two parts, the Test and the Result if True. The test comes prior to the keyword of Then and the Result if True comes after.
Parameter is divided into two parts, the Test and the Result if True. The test comes prior to the keyword of Then and the Result if True comes after.
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc..]
Takes two parameters, FieldBase, FieldNamesList
Takes 4 parameters, FieldBase, Left, Comparison, Right
Takes five parameters, FieldBase, FieldList, Mask, bBlanks2Zero, IfLenFld
Takes one parameter, bNoHeaders
Takes one parameter, a List of possible group types
Takes one parameter, Source
Takes two parameters, TableName, IfLenFld
Takes four parameters, DestinationTable, SourceTable, bWithParents, bWithPWHashes
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc...]
A command to help build spreadsheets
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bUseContainer, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes two parameters, FileName, bUseHeader
Takes two parameters, FilePath, bUseHeader
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Has one parameter, Options
Takes a variable number of conditional statements
Parameter is a comma separated list (using CSV rules and not in quotes) of the options made available to the user which are enforced on save.
Takes 3 parameters, QueryName, SourceQuery, bWork
Takes a single Field name, with an optional Not operator, followed by the conditional statement
Prerequisites: This page assumes that you have already set up your Moxie.Build server and logged in as an admin user. This page covers some of the basics that are involved in using the Content Management aspects of the Moxie.Build system.
Developing in Moxie.Build on localhost give you the advantage of working with the template files natively. When working on procedures (MOX code) you need to access that through the Procedures page in the Admin area of a Moxie.Build system, if running the server on localhost or on a remote server. When running on a remote server, you can edit the template files via the Files page in the Admin area.
Takes no parameters
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 bNoHeaders and returns the result to an assigned variable
Takes three parameters Method, URL, Body
Takes one parameter, a Source value
Takes two parameters: Username, GroupTypes
Takes one parameter, FieldName
Takes a variable number of conditional statements to compare against a single source
Takes one parameter, TestCondition
A .mox file, with MOX code in it, can be run from the command line while a Moxie.Build system is not otherwise already running.