Takes 4 parameters, FieldBase, Destination, SourceFields, Delimiter
Takes one parameter, FieldBaseToTrim
Takes two parameters, FieldBase, FieldNames
Takes three parameters, FieldBase, Destination, SourceFields
Takes two parameters, FieldBase, FieldNamesList
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes one parameter, FieldName
Takes one parameter, a comma separated list of FieldNames
Takes one parameter, FieldName
Parameter is a space separated list of field names to be displayed when the user is viewing results from the Search List in the Admin interface.
Takes one parameter, a FieldBase
Parameter is a single new field name or a space separated list of new field names.
Takes three parameters, QueryName, FieldBase, FieldNames
Parameter is a space separated list of field names to be displayed.
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, DestinationFields, SourceFields
Takes two parameters, FieldBase, FieldNames
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes two parameters, TableName, FieldList
Takes two parameters, FieldBase, FieldNameList
Takes two parameters, a TableName and FieldName
Takes two parameters, FieldBase, FieldNames
Parameter is the table and field name that you want to sum in the form of TableName.FieldName. The specified Table must be a Child of the calling Record.
Takes one parameter, TableName
Takes no parameters
Allows any extra HTML Attributes to be specified in the Control's HTML Tag
Takes one parameter, TableName
Has no parameters.
Takes one parameter, a single character
Takes one parameter, a Source value
Takes one parameter, Source value
Has no parameters
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Fields
Takes one parameter.
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.
Has no parameters.
Has no parameters.
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.
Has no parameters.
Has no parameters.
Has no parameters.
Takes 1 parameter, a formatting mask
Has no parameters.
Takes 1 parameter, a formatting mask
Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld
Takes a single Field name, with an optional Not operator, followed by the conditional statement
Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
Takes three parameters, TableName, SearchTerms, SearchInFields
Takes one parameter, in the form of: Table|{Alias}|Field
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes four parameters, DestinationQuery, SourceQuery, UniqueField, UniqueValue
Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes five parameters, FieldBase, FieldList, Mask, bBlanks2Zero, IfLenFld
Takes a single parameter, a FieldBase
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes 5 parameters, FieldBase, FolderPath, Action, Source, IfLenFld
Takes up to 6 parameters, FieldBase, Destination, Action, Source, Value, IfLenField
Takes one parameter, FieldName
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc...]
Takes one parameter, FieldBase
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes 3 parameters, FieldBase, pOne, pTwo
Some Work Query command parameters can accept a source of either a Work Query Field name or a text literal. Text literals in these cases are prefixed with a backtick ` character.
Takes one parameter, FieldName
Takes 4 parameters, FieldBase, Left, Comparison, Right
Parameter is a space separated list of fields to choose from
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
Takes one parameter, FieldBase
Takes one parameter, FieldBase
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc..]
Has no parameters.
Accepts one parameter which is the raw HTML content to be placed in the form, below the Field's location.
Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.
Has no parameters.
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.
Parameter is a space separated list of field names to have the display table sorted by when displaying search results in the Admin interface.
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes two parameters, FieldName, Value
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes five parameters, FieldBase, Destination, Action, Source, IfLenFld
Parameter must first specify only looking at Parents ( PARENT ) or only looking at Children ( CHILD ). The remainder of the parameter should be the table and field name you are after in the form of TableName.FieldName.
Takes one parameter which is the keyboard key which will be used as the Access Key for a given Database Table's field.
*Note: By default, each Field's Access Key will be initialized to the first character of the Field's Label.
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes two parameters, FieldBase, SortFieldList
Takes four parameters, FieldBase, FieldName, Source, IfLenFld
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes three parameters, FieldBase, Fields, IfLenFld
Takes three parameters, FieldBase, Fields, IfLenFld
Accepts a space separated list of field names.
Takes three parameters, QueryName, FieldBase, FieldNames
Takes two parameters, FieldBase, PivotField
Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld
Takes 6 parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes two parameters, WorkFieldBase + FieldToParse, Delimiter
Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld
Has no parameters. If the field is blank it will remain blank.
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes two parameters, TableName, IfLenFld
Takes two parameters, Name, Value
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes three parameters, TableName, Alias, Password
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes a variable number of parameters
Takes two parameters, CSVData, bNoHeaders
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes two parameters, Location, Mode
Takes one parameter, Data
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes two parameters, Data, bHasHeader
Takes one parameter, TableName
Takes one parameter, TableName
Takes no parameters
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes two parameters, TableName, IfLenFld
Has no parameters
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bUseContainer, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes two parameters, TableName, IfLenFld
Takes no parameters.
Takes two parameters, FileName, bHasHeader
Has no parameters
Has no parameters
Takes two parameters, FileName, bHasHeader
Takes two parameters, Data, Options
Takes one parameter, FilePath
Takes two parameters, Data, Boundary
Takes two parameters, FileName, Options
Takes no parameters
Takes two parameters, FilePath, bUseHeader
Takes two parameters, FileName, bHasHeader
Takes two parameters, FileName, bHasHeader
Takes 3 parameters, Folder, Filter, bShowImgSize, bShowAccessed
Takes two parameters, FileName, bHasHeader
Takes two parameters, ExcelTableData, Options
Takes two parameters, FileName, bUseHeader
Takes two parameters, CSVData, bNoHeaders
Takes two parameters, [WorkWith]+Scope, EmbedScope
Takes no parameters
Takes two parameters, FileName, bUseHeaders
A command to help build spreadsheets
Takes two parameters, FileName, bUseHeader
Takes a variable number of parameters
Takes two parameters, FileName, bHasHeader
Takes two parameters, CSVData, bNoHeaders
Takes two parameters, Data, bHasHeader
Takes two parameters, TableName and a boolean expression
Takes 3 parameters, DestinationQuery, SourceQuery, bMoveIt
Takes two parameters, FileName, FileData
Has no parameters
Takes three parameters, FolderPath, Action, Source
Takes three parameters, Destination, Action, Source
Has no parameters
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.
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.
A Message Handler is only ever called by the Database on a Database Event. These Event Messages allow a Developer to intercept operations taking place on a per-record level and implement Event based business logic.
In this example, you will see how to use a public method that works on or with the current WorkQuery that you pass into the method.
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.
A Remote Method may be called by any other Moxie system. It can be used to divide up a large system among a number of backend servers, or as a public API for 3rd parties. In order to call a Remote Method from MOX, the Remote statement is used.
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes one parameter, QueryName
Takes one parameter, Control
Takes one parameter, QueryName
Takes a variable number of conditional statements to compare against a single source
Takes two parameters, FileName, FileData
Takes a variable number of parameters.
Has 4 parameters, Destination, Action, Source, Value
Takes a variable number of conditional statements
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
Takes five parameters, DestQuery, SourceQuery, SourceXFld, SourceYFld, SourceZFld
Takes six parameters, DestQuery, SourceQuery, DestDestFld, DestXFld, DestYFld, SourceYFld
Has one parameter, a Content.Lang prefix
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.
In order for source code to be more readily readable across teams, it is recommended that your source code always be styled according to this style guide.
Parameter is a value or an expression to be used when a record is created if no value is specified during the creation. The value or expression is run through the Assignment Attribute in order to calculate it's result.
Takes 3 parameters, Event, DestinationID, Path
Prerequisites: This tutorial assumes that you have already learned about Managing Files .
Prerequisites: This tutorial assumes that you have already set up a Category and Procedure if necessary. This page covers some of the basics that are involved in Front End development using the MOX language.
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.
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.
Prerequisites: This tutorial assumes that you have already set up your Moxie.Build server and logged in. This page covers some of the basics that are involved in managing files and folders in the Moxie.Build system.
Takes no parameters
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
Takes one parameter.
Accepts 3 parameters, first is required, 2nd and 3rd are optional. A trailing optional expression after an = sign may also assign a value on the same line.
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.
Takes two parameters, FileName, bHasHeader
Brief overview on the file structure and contents under Moxie. The files and folders discussed in this post are those that are essential when upgrading to the most recent version of Moxie.Build , or when troubleshooting server errors.
Accepts a numeric value as a parameter.
Accepts a numeric value as a parameter.
Has no parameters.
Has no parameters.
Takes one parameter
Accepts one optional numeric value as a parameter
Takes two parameters Command, Options
Takes one parameter, a List of possible group types
Takes one parameter, a top query destination variable
Takes two parameters, Source, Value
Takes two parameters, Source, Value
Takes one parameter, bNoHeaders
Takes one parameter, a Date value
Takes three parameters, FilePath, Start, Len
Takes one parameter, a Source value
Takes three parameters, TableName, Alias, Password
Takes one parameter, Index
Takes one parameter, bNoHeader
Takes two parameters, Source, Value
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes one parameter, TableName
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes two parameters, ChildTableName, Mode
Takes two parameters, ChildTableName, Mode
Has no parameters
Takes two parameters, Location, Mode
Takes one parameter, Source
Takes two parameters, Source, Value
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes 6 parameters, Location, Mode, ActionPath, Name, Class, Prompt
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
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 one parameter, TestCondition
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, Message, or no parameters
Takes no parameters
Takes one parameter.
Cloudflare automatically provides free client-facing certificates for your domain, even if using their free service. In addition, they provide free Origin Certificates to encrypt the connection between Cloudflare and your origin Moxie.Build server. Use this article if you are going to have Cloudflare connect to inbound open ports on your Moxie.Build server.
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
Takes one parameter, SlowWritePercent
Takes no parameters.
The Setup Table controls aspects that can be changed while the server is running, and is intended to contain both Moxie.Build specific values as well as application specific.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes either one parameter, ResultValue, or no parameters
Has one parameter, Options
Has two parameters: Source, Options
Has two parameters: Source, Options
Takes two parameters, Source, Search
Takes two parameters, Source , Search
Takes one parameter, Source
Takes either one parameter, ResultValue, or no parameters
Takes one parameter, Message, or no parameters
Takes no parameters
Takes five parameters, Lat1, Long1, Lat2, Long2, Options
Has one parameter.
Takes one parameter bNoHeaders and returns the result to an assigned variable