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, ParentTableName, ChildTableName, IfLenFld
Takes two parameters, TableName and a boolean expression
Takes one parameter, TableName
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes one parameter, TemplateData
Takes one parameter, TableName
Takes two parameters, TableName, IfLenFld
Takes one parameter, TableName
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes one parameter, TableName
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 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 one parameter, FieldBase
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 three parameters Method, URL, Body
Takes three parameters, Location, ClassNames, AlertText
Takes two parameters, Title, Path
Takes one parameter, bNoHeaders
Takes one parameter bNoHeaders and returns the result to an assigned variable
Takes one parameter, a top query destination variable
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes four parameters, FieldBase, FieldName, Source, IfLenFld
Takes two parameters, FileName, bUseHeaders
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes two parameters, FieldBase, PivotField
Takes two parameters, Name, Value
Takes two parameters, TableName, IfLenFld
Takes two parameters, Name, Value
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes no parameters
Takes two parameters, WorkFieldBase + FieldToParse, Delimiter
Takes 3 parameters, Folder, Filter, bShowImgSize
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
Takes two parameters, Data, Options
Takes two parameters, FileName, FileData
Takes one parameter
Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.
Prerequisites: This tutorial assumes that you have already learned about Managing Files .
Takes 3 parameters, Trigger, DestinationID, Path
Has no parameters
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
Parameter is a single new field name or a space separated list of new field names.
Accepts a space separated list of field names.
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.
A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.
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.
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".
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.
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.
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 five parameters, DestQuery, SourceQuery, SourceXFld, SourceYFld, SourceZFld
Takes one parameter, QueryName
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
Has one parameter, a Content.Lang prefix
Takes one parameter, QueryName
Takes a variable number of parameters.
Takes 3 parameters, QueryName, SourceQuery, bWork
Used as a scoping keyword, similar to WorkWith/End WorkWith .
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 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.
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.
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.
Takes 3 parameters, DestinationQuery, SourceQuery, bMoveIt
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
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.
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.