Takes one parameter, Source value
Takes one parameter, a Source value
Has no parameters.
Has no parameters.
Has no parameters.
Has no parameters.
Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld
Takes 6 parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes one parameter, FieldBase
Takes three parameters, FieldBase, Destination, SourceFields
Takes a single parameter, a FieldBase
Takes three parameters, FieldBase, Fields, IfLenFld
Takes three parameters, QueryName, FieldBase, FieldNames
Takes one parameter, FieldBase
Takes one parameter, FieldBase
Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld
Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost
Takes up to 6 parameters, FieldBase, Destination, Action, Source, Value, IfLenField
Takes five parameters, FieldBase, FieldList, Mask, bBlanks2Zero, IfLenFld
Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc..]
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc...]
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
Takes 4 parameters, FieldBase, Left, Comparison, Right
Takes 3 parameters, FieldBase, pOne, pTwo
Takes two parameters, FieldBase, FieldNameList
Takes 4 parameters, FieldBase, Destination, SourceFields, Delimiter
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes 5 parameters, FieldBase, FolderPath, Action, Source, IfLenFld
Takes two parameters, FieldBase, FieldNames
Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld
Accepts a space separated list of field names.
Takes five parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Has no parameters.
Allows any extra HTML Attributes to be specified in the Control's HTML Tag
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes 1 parameter, a formatting mask
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes two parameters, FieldBase, SortFieldList
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes four parameters, FieldBase, FieldName, Source, IfLenFld
Takes four parameters, FieldBase, Destination, Source, IfLenFld
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 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.
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes three parameters, QueryName, FieldBase, FieldNames
Takes two parameters, FieldBase, FieldNames
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes 1 parameter, a formatting mask
Has no parameters.
Has no parameters.
Has no parameters.
Takes two parameters, FieldBase, FieldNames
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, FieldBase, PivotField
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes three parameters, FieldBase, Fields, IfLenFld
Takes two parameters, FieldBase, FieldNamesList
Takes one parameter, FieldBaseToTrim
Takes one parameter, a FieldBase
Upgrade Notes
In order to Upgrade an existing copy of Moxie.Build V4 or V5 to the most recent version of V5, you can use the Upgrade example files found in the Tools folder to help automate upgrading multi-service systems, or you can just replace the following files/folders:
Moxie.exe
Moxie.dll
Default.dll
/DBStore/BuiltIn.*
/Lib
/Public/BuiltIn
/Templates/Admin
/Templates/Clean
/Templates/Default
/Templates/Default5
/Templates/Report
Takes two parameters, WorkFieldBase + FieldToParse, Delimiter
Takes two parameters, DBTableName, DBTableRecordAlias
Takes two parameters, FileName, Options
Takes a variable number of parameters
Takes two parameters, FileName, bHasHeader
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 one parameter
Accepts one optional numeric value as a parameter
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 a variable number of conditional logical if statements
Has no parameters
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.
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 a numeric value as a parameter.
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 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.
Takes one parameter, Name
Takes one parameter, a List of possible group types
Has no parameters
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes one parameter, a single character
Takes a variable number of parameters
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
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.
Takes a variable number of conditional statements to compare against a single source
Takes one parameter, Control
Some Work Query command parameters can accept a source of either a Work Query Field name or a text literal. Text literals in these cases are prefixed with a backtick ` character.
Takes two parameters, Source, Value
Takes two parameters, Source, Search
Has one parameter, Options