Takes one parameter, the text of the error to throw.
Used as a scoping keyword, similar to WorkWith/End WorkWith .
Takes one parameter.
Has no parameters
Takes 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 , or when troubleshooting server errors.
A traditional way to check for hard errors and enable those errors to error softly.
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. To use different values than labels, for each comma separated pair, specify the value first inside of { } followed by the label.
If the Parameter is just the single word Checkbox, then instead of a drop down list with values, the user will be given a single checkbox: If the field is unchecked the value will be blank, and if it is checked the value will be "y".
When this attribute is used with a Top Query in MOX, it will ensure the field value matches one of the options; if not, it will throw a run time error.
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes three parameters, TableName, Alias, Password
Takes three parameters, Login, Password, bRememberMe
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes one parameter, Source
Takes one parameter, TableName
Takes two parameters, Title, Path
Takes one parameter, ErrMsg
Takes three parameters, Location, ClassNames, AlertText
Takes two parameters, TableName and a boolean expression
Has no parameters
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld
Takes no parameters.
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes two parameters, FieldBase, FieldNames
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes two parameters, FieldBase, FieldNames
A command to help build spreadsheets
Takes two parameters, FromIndex, ToIndex
Takes two parameters, TableName, IfLenFld
Takes three parameters, TableName, Alias, Password
Takes two parameters, TableName, IfLenFld
Takes three parameters, Login, Password, bRememberMe
Takes two parameters, FieldBase, FieldNameList
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, TableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
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.
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
Takes one parameter, the Name of the critical section
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Takes two parameters, SubjectPrefix, EmailBody
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.
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.
Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.
Takes 3 parameters, Trigger, DestinationID, Path
Takes one parameter, a Label
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 Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running
Takes one parameter, TestCondition
Takes five parameters, Lat1, Long1, Lat2, Long2, Options
Takes one parameter.
Takes one parameter, QueryName
Has one parameter.
Takes one parameter, Value
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.
Takes one parameter, OutputText