Parameter is a space separated list of field names to be displayed.
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.
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 one parameter, TableName
Takes three parameters, QueryName, FieldBase, FieldNames
Has no parameters
Takes one parameter, TableName
Takes two parameters, FolderPath, bRecursive
Takes 3 parameters, Folder, Filter, bShowImgSize
Takes one parameter, TableName
Takes no parameters
Takes no parameters
Has no parameters
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 two parameters, FieldBase, FieldNamesList
Takes one parameter, a List of possible group types
Takes two parameters, TableName, RltnList
Parameter is a single new field name or a space separated list of new field names.
Takes two parameters, TableName, FieldList
Parameter is a comma separated list (using CSV rules and not in quotes) of the fixed hard coded values to select from
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Takes two parameters, TableName, ProcList
Accepts a space separated list of field names.
Takes one parameter, a comma separated list of FieldNames
Takes five parameters, FieldBase, FieldList, Mask, bBlanks2Zero, IfLenFld
Takes two parameters, FieldBase, SortFieldList
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, FieldBase, FieldNameList
Parameter is a space separated list of fields to choose from
This list of examples is going to grow over time. We are open to requests, as well as submissions if you have something you would like to share.
In this example, we use a plain old Moxie.Build system and compare it to the MEAN Stack equivalent by building two functionally equivalent versions of a fleshed out To Do List Application. Both versions utilize local user authentication, a relational database system and the security measures found in typical production-level applications on the web today.
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes two parameters, a TableName1 and TableName2
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes two parameters, TableName, IfLenFld
Has no parameters.
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes three parameters, Login, Password, bRememberMe
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source, Value
Takes two parameters, Source, Value
Takes two parameters, Source, Value
Takes one parameter, bNoHeaders
Takes one existing Source value, and two parameters of equal length, SearchVals, NewVals
Takes one existing Source value, and two parameters, Search, NewVal
Takes one parameter, EscapedTemplate, and returns the Unescaped Version of this string
Takes two parameters, Source, Value
Takes one parameter, Source
Takes one parameter, Source
Takes one parameter, Name
Has no parameters
Takes one parameter, Type
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes two parameters, ChildTableName, Mode
Takes two parameters, a TableName and ProcName
Takes one parameter, TableName
Takes two parameters, ChildTableName, Mode
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes two parameters, Source, AllowedCharacters (case sensitive)
Takes two parameters, Source, AllowedCharacters (case sensitive)
Takes two parameters, Source, Search
Takes one parameter, Source
Takes one parameter, ErrMsg
Takes two parameters, Location, Mode
Takes three parameters, Location, ClassNames, AlertText
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes two parameters, FileName, bUseHeader
Takes two parameters, FileName, Options
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes two parameters, CSVData, bNoHeaders
Takes two parameters, Data, bHasHeader
Takes three parameters, FieldBase, Fields, IfLenFld
Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld
Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld
Takes two parameters, FilePath, bUseHeader
Takes three parameters, QueryName, FieldBase, FieldNames
Takes three parameters, FieldBase, Fields, IfLenFld
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes four parameters, FieldBase, Destination, Source, IfLenFld
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 five parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes two parameters, Location, Mode
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld
Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes two parameters, ExcelTableData, Options
Takes two parameters, Data, Options
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes two parameters, CSVData, bNoHeaders
Takes two parameters, CSVData, bNoHeaders
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes two parameters, FileName, bHasHeader
Takes two parameters, FileName, bHasHeader
Takes one parameter, FilePath
Takes 6 parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes a variable number of parameters
Takes two parameters, FileName, bHasHeader
Takes no parameters
Takes no parameters
Takes two parameters, FileName, bHasHeader
Takes two parameters, PathToFile, Options
Takes two parameters, FileName, bHasHeader
Takes one parameter, HtmlEscapedString, and returns the Unescaped Version of this string
Takes a variable number of conditional statements to compare against a single source
Fields
Takes one parameter, SlowWritePercent
Takes one parameter, OutputText
Takes two parameter, URL, InputQuery
Takes one parameter, QueryName
Takes a variable number of conditional statements
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes a single Field name, with an optional Not operator, followed by the conditional statement
Takes a single string as parameter, which is then appended to each line in the code block.
Takes one parameter, QueryName
This utility program manages a server install with one or many Moxie.Build services running by taking care of nightly tasks via a scheduled task.
The optional Moxie.http file is read on server start and controls the default HTTP headers set for all requests.
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.
Takes one parameter, TestCondition
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.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes one parameter, FieldBase
Takes one parameter, FieldName
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
Cloudflared Tunnel exposes applications running on your local web server on any network with an internet connection with an outbound tunnel that connects directly to Cloudflare's edge network without the need to configure inbound firewall rules.
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.
Prerequisites: This tutorial assumes that you have already learned about Managing Files .
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.
Has no parameters.
Accepts a numeric value as a parameter.
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.
Markdown enables simple formatting of plain text via easy to remember conventions. This page will provide you with some pointers on what formatting options are available with "Moxie Flavored Markdown".
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.
A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.
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.
Takes 2 parameters, Result, Status
Takes one parameter, the name of the query
Has no parameters
Takes two parameters, FolderPath, Action
Takes 3 parameters, Destination, Action, Source
Takes 3 parameters, DestinationQuery, SourceQuery, bMoveIt
Takes two parameters, FileName, bHasHeader
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
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.
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.
A Public Method may be called from any other Procedure, by the Default plug-in, or a Custom COM DLL. Each Public Method may either use specific Input Parameters, or it may accept an Input Query.
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 two parameters, Source, Value
Takes two parameters, Source, Search
Takes one parameter, a Source value
Takes one parameter, a Date value
Takes one parameter, a Source value
Takes two parameters, Source , Search
Has two parameters: Source, Options
Has two parameters: Source, Options
Has one parameter, Options
Takes one parameter, Source
Has one parameter.
Takes three parameters, TableName, Alias, Password
Takes one parameter, Source
Takes one parameter, a top query destination variable
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, Source
Takes two parameters, Source and Match
Takes one parameter, in the form of: Table|{Alias}|Field
Takes two parameters, Source and Match
Takes two parameters, Source and Match
Takes two parameters, Source and Match
Takes two parameters: Username, GroupTypes
Has one parameter.
Takes one parameter bNoHeaders and returns the result to an assigned variable
Has no params
Takes two parameters, Source , Search
Takes two parameters, Source, Search
Takes two parameters, User and Password
Takes no parameters
Takes no parameters
Has no params
Takes three parameters Method, URL, Body
Takes one parameter
Takes one parameter, FieldName
Has one parameter
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
Has no parameters
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes one parameter, a date of the form yyyy-mm-dd
Takes five parameters, Lat1, Long1, Lat2, Long2, Options
Takes one parameter, a gregorian number
Takes no parameters
A type of Prefix which allows the developer to separate blocks of code into organized, defined parts to help provide clarity of the logical block and add structure to the code.
A PaaS Method may be called by any other Moxie system. In order to call a PaaS Method from MOX, the PaaS statement is used.