Takes 1 parameter, a formatting mask
Takes 1 parameter, a formatting mask
Takes 1 parameter, a formatting mask
Takes 1 parameter, a formatting mask
Takes two parameters, a source value, and a formatting mask.
Takes five parameters, FieldBase, FieldList, Mask, bBlanks2Zero, IfLenFld
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Accepts one parameter which is the raw HTML content to be placed in the form, below the Field's location.
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".
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.
Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.
Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.
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.
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, in the form of: Table|{Alias}|Field
Takes one parameter, a date of the form yyyy-mm-dd
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes 6 parameters, Location, Mode, ActionPath, Name, Class, Prompt
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes one parameter, a gregorian number
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
Has two parameters: Source, Name
Takes no parameters
Takes two parameters, Location, Mode
Takes two parameters, Title, Path
Takes one parameter, the contents of which are used for the HTTP Reply Body
Takes one parameter, a value in number of bytes.
Takes one parameter, TableName
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes one parameter, FieldName
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes five parameters, Lat1, Long1, Lat2, Long2, Options
Takes three parameters, Location, Mode, TemplateName
Takes one parameter, Name
Takes four parameters, DestinationTable, SourceTable, bWithParents, bWithPWHashes
Takes one parameter, Type
Takes one parameter, ErrMsg
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, a top query destination variable
Takes three parameters, Login, Password, bRememberMe
Takes one parameter, bNoHeaders
Takes one parameter, EscapedTemplate, and returns the Unescaped Version of this string
Takes one parameter, a Date value
Takes two parameters, Source, Search
Takes one parameter, bNoHeader
Takes one parameter, Source
Takes one parameter, Source
Takes one parameter, Source
Takes one parameter, Source
Takes two parameters, Source, Value
Takes one parameter, a Source value.
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes one parameter, Source
Has one parameter, Options
Takes one parameter, Source
Has two parameters: Source, Options
Takes two parameters, Source, Value
Takes two parameters, Source, Value
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes two parameters, FilePath, bUseHeader
Takes three parameters, FieldBase, Fields, IfLenFld
Takes two parameters, FileName, Options
Takes two parameters, FileName, bUseHeader
Takes two parameters, FileName, bUseHeaders
Takes three parameters, FieldBase, Fields, IfLenFld
Takes two parameters, Data, bHasHeader
Takes one parameter, QuantityToAdd
Takes two parameters, WorkFieldBase + FieldToParse, Delimiter
Takes two parameters, FieldBase, PivotField
Takes three parameters, FieldBase, Destination, SourceFields
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes 5 parameters, Location, Mode, Title, Element, Class
Has no parameters.
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bUseContainer, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes two parameters, CSVData, bNoHeaders
A command to help build spreadsheets
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes five parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes two parameters, FieldBase, FieldNamesList
Takes 5 parameters, FieldBase, FolderPath, Action, Source, IfLenFld
Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost
Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld
Takes two parameters, CSVData, bNoHeaders
Takes no parameters
Takes two parameters, Name, Value
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes up to 6 parameters, FieldBase, Destination, Action, Source, Value, IfLenField
Takes two parameters, FileName, bHasHeader
Takes two parameters, Data, Boundary
Takes one parameter, FilePath
Takes two parameters, FileName, bHasHeader
Has no parameters
Takes two parameters, FileName, bHasHeader
Takes 4 parameters, FieldBase, Left, Comparison, Right
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes no parameters
Takes 3 parameters, Folder, Filter, bShowImgSize, bShowAccessed
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.
Accepts a numeric value as a parameter.
Takes one parameter.
Has no parameters.
Has no parameters.
Takes one 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.
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.
Accepts a numeric value as a parameter.
Has no parameters.
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.
Effective Websites. Downtown Quality, Small Town Affordability.
Takes two parameters, SubjectPrefix, EmailBody
Has no parameters
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.
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.
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.
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.
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.
Moxie.Build, in short, may be used and licensed free of charge for education and non-profit organizations. Whenever it is used by government or for-profit organizations the license is granted on a subscription basis.
Moxie.Build includes a number of open source components as part of its distribution; each is subject to their own licenses as included with the files for those components.
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.
This is our current Privacy Policy, last updated 2016-01-12.
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.
Has no parameters.
Has no parameters.
Takes no parameters
Has no parameters.
Has no parameters.
Has no parameters.
This is our current Terms of Service, last updated 2016-01-12.
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.
Has no parameters.
Takes 3 parameters, Event, DestinationID, Path
Takes one parameter, Source
Takes one parameter, TestCondition
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
The optional Moxie.http file is read on server start and controls the default HTTP headers set for all requests.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
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.
Has no parameters. If the field is blank it will remain blank.
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.
Has one parameter.
Takes one parameter bNoHeaders and returns the result to an assigned variable
Takes one parameter, a numeric value
Takes one parameter, a string containing a date and time
Takes one parameter, a string containing a date and time
Takes one parameter
Takes one parameter.
Has no params
Takes two parameters, User and Password
Takes three parameters Method, URL, Body
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
Takes a single parameter, a FieldBase
Takes a variable number of conditional statements
Has one parameter.
Has 4 parameters, Destination, Action, Source, Value
Has no parameters
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Takes three parameters, Destination, Action, Source
Takes a single parameter, a QueryName
Takes three parameters, FolderPath, Action, Source
A traditional way to check for hard errors and enable those errors to error softly.
Takes one parameter, Value
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.
Takes one parameter, Control
Takes any unspecified data, intended for use by external systems
Takes a variable number of parameters.
Takes one parameter, ServerLogText
Takes a variable number of conditional statements to compare against a single source