Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source and Match
Takes two parameters, Source, Match
Takes two parameters, Source and Match
Takes two parameters, Source and Match
Takes two parameters, Source and Match
Takes two parameters, ChildTableName, Mode
Takes two parameters, TableName and a boolean expression
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes two parameters, ChildTableName, Mode
Takes three parameters, TableName, SearchTerms, SearchInFields
Takes two parameters, TableName, IfLenFld
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes two parameters, TableName, IfLenFld
Takes one parameter, Name
Takes 2 parameters, pNum1, pNum2
Takes two parameters, Source, Search
Takes one parameter, a List of possible group types
Takes two parameters, Source, Options
Takes one parameter, TableName
Takes 2 parameters, pString1, pString2
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.
Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld
Takes three parameters, QueryName, FieldBase, FieldNames
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes two parameters, FileName, Options
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, FromIndex, ToIndex
Takes two parameters, FieldBase, FieldNameList
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
Takes 3 parameters, Folder, Filter, bShowImgSize, bShowAccessed
Takes one parameter, FieldBaseToTrim
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc...]
Takes one parameter, FieldName
Takes two parameters, Source , Search
Takes a variable number of parameters
Takes one parameter, Source
Takes two parameters, Source, Search
Takes 3 parameters, DestinationQuery, SourceQuery, bMoveIt
Has two parameters: Source, Name
Has two parameters: Source, Options
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.
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
Takes three parameters, QueryName, FieldBase, FieldNames
Takes a variable number of parameters
Takes four parameters, DestinationQuery, SourceQuery, UniqueField, UniqueValue
Takes six parameters, DestQuery, SourceQuery, DestDestFld, DestXFld, DestYFld, SourceYFld
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Parameter is a comma separated list (using CSV rules and not in quotes) of the fixed hard coded values to select from
Takes two parameters, User and Password
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.
Takes two parameters, Source and Search
Moxie.Build supports translating any user-facing text into multiple languages from a single database table. Procedures, templates, and database field metadata all share the same translation store, so a string written once is reusable everywhere.
Takes two parameters, Source and Search
Takes two parameters, Source, Search
Takes one existing Source value, and two parameters of equal length, SearchVals, NewVals
Takes two parameters, Source and Search
Takes two parameters, Source, Search
Takes two parameters, Source, Search
Takes two parameters, Source, Search
Has one parameter, Options
Takes one parameter, Source
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.
This style guide provides comprehensive standards for writing clean, maintainable, and consistent MOX code for Moxie.Build. Code examples on this page are for illustrative purposes and are only intended to demonstrate style conventions.