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.
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 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.
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.
Web/API Development Platform with an in-memory database, native-code CMS, and a powerful runtime environment Whether you are a new startup taking off or optimizing your business model for growth, Moxie.Build provides a robust platform with a proven track record for marketplaces, eCommerce, and business process automation
Takes one parameter, the name of a database table
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 one parameter, TableName
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, TableName
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes two parameters, a TableName and FieldName
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes one parameter, TemplateData
Takes two parameters, Title, Path
Takes two parameters, Source, Value
Takes one parameter, TableName
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Has no parameters
Takes two parameters, Source, Value
Takes one parameter, EscapedTemplate, and returns the Unescaped Version of this string
Takes two parameters, TableName and a boolean expression
Takes one parameter, HtmlEscapedString, and returns the Unescaped Version of this string
Takes two parameters, Source, Value
Takes two parameters, Source, Value
Takes one parameter, Name
Takes one parameter, TableName
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes one parameter, QuantityToAdd
Takes three parameters, FieldBase, Fields, IfLenFld
Takes 4 parameters, FieldBase, Left, Comparison, Right
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes one parameter, FilePath
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes no parameters
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes four parameters, TableName, Relation, OtherTableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Takes three parameters, TableName, Alias, Password
Takes one parameter, TableName
Has no parameters
Takes one parameter, TableName
Takes one parameter, TableName
Takes two parameters, TableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes three parameters, TableName, SearchTerms, SearchInFields
Takes two parameters, Name, Value
Takes no parameters
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.
Takes 1 parameter, a formatting mask
Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.
Has no parameters.
Has no parameters
Accepts a numeric value as a parameter.
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 1 parameter, a formatting mask
Takes 3 parameters, Trigger, DestinationID, Path
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.
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 one parameter which is the raw HTML content to be placed in the form, below the Field's location.
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.
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.
Takes one parameter.
Takes one parameter, FieldName
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes no parameters.
Takes three parameters, TableName, Alias, Password
Takes one parameter, a top query destination variable
Takes one parameter, Source
Takes one parameter, in the form of: Table|{Alias}|Field
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.
Has no parameters
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.
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.
Takes a variable number of parameters
A traditional way to check for hard errors and enable those errors to error softly.
Takes any unspecified data, intended for use by external systems
Used as a scoping keyword, similar to WorkWith/End WorkWith .