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. 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 used with a Top Query in MOX, this will ensure the field value matches one of the options, if not it will throw a run time error.
Parameter is a space separated list of field names to be displayed when the user is viewing results from the Search List.
Parameter is a space separated list of field names to be displayed.
Takes two parameters, FolderPath, bRecursive
Takes 3 parameters, Folder, Filter, bShowImgSize
Takes no parameters
Has no parameters
Takes no parameters
Takes three parameters, QueryName, FieldBase, FieldNames
Used as a Relationship Attribute, the parameter is a space separated list of field names
Learn how your development shop can build awesome solutions for engaged customers, and get listed as a Moxie.Build Partner on this website.
Parameter is a space separated list of field names to have the display table sorted by when displaying search results.
Takes two parameters, FieldBase, FieldNameList
Takes two parameters, FieldBase, FieldNamesList
Takes one parameter, a List of possible group types
Takes one parameter, a comma separated list of FieldNames
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Accepts a space separated list of field names.
Parameter is a single new field name or a space separated list of new field names.
Takes five parameters, FieldBase, FieldList, Mask, bBlanks2Zero, IfLenFld
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, FieldBase, SortFieldList
This list of examples is going to grow over time. We are open to requests, as well as submissions if you have something you would like to share.
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 two parameters, a FieldBase and FieldNamesList
Download Free Download of Moxie.Build Delivered as a simple .zip file, so that you can set it up however you like. This approach allows you to custom install many services on one server , or just run it as an app without an install.
Release Notes
All recent changes to Moxie.Build are documented in the Confirmed for Next Release list on our public Trello Board
In order to Upgrade an existing copy of Moxie.Build V4 to the most recent version, you can use our Upgrade system that is designed to help automate 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/Report
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes two parameters, Source, Match
Takes one parameter, Source
Takes one parameter, Source
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source, AllowedCharacters (case sensitive)
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes two parameters, Source, Match
Takes two parameters, Source, Search
Takes two parameters, Source, AllowedCharacters (case sensitive)
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes two parameters, Source and Match
Takes two parameters, Source and Match
Takes one parameter, Source
Takes one parameter, in the form of: Table|{Alias}|Field
Takes two parameters, Source and Match
Takes two parameters, Source and Match
Takes one parameter, Source
Takes one existing Source value, and two parameters, Search, NewVal
Takes one existing Source value, and two parameters of equal length, SearchVals, NewVals
Takes two parameters, Source, Value
Takes one parameter, a top query destination variable
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Has no parameters
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes a variable number of parameters
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes no parameters
Takes three parameters, QueryName, FieldBase, FieldNames
Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld
Takes three parameters, FieldBase, Fields, IfLenFld
Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld
Takes three parameters, FieldBase, Fields, IfLenFld
Takes 6 parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes no parameters
Takes five parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes two parameters, ChildTableName, Mode
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes two parameters, TableName, IfLenFld
Takes two parameters, ExcelTableData, Options
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes two parameters, Location, Mode
Has no parameters
Takes 3 parameters, Destination, Action, Source
Takes two parameters, FolderPath, Action
Takes 3 parameters, DestinationQuery, SourceQuery, bMoveIt
Takes one parameter, the name of the query
Takes 2 parameters, Result, Status
Takes a single string as parameter, which is then appended to each line in the code block.
Takes two parameter, URL, InputQuery
Takes one parameter, OutputText
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes a variable number of conditional statements
Takes a single Field name, with an optional Not operator, followed by the conditional statement
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.
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 using the Content Management aspects of the Moxie.Build system.
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.
Web Portals & Databases
Accepts a numeric value as a parameter.
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.
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.
The MOX 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 learned about Managing Files .
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 two parameters, Source, Match
Takes two parameters: Username, GroupTypes
Has two parameters: Source, Options
Takes one parameter, a gregorian number
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, [ContentType], [extraHeader], [body], [rtnHeaders]
Takes two parameters, Source, Match
Takes one parameter, a Source value
Takes one parameter, a Source value
Takes one parameter, a Date value
Takes two parameters, Source , Search
Takes two parameters, Source, Search
Takes two parameters, Source, Value
Takes one parameter, a date of the form yyyy-mm-dd
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
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 one parameter, TestCondition
Takes one parameter, FieldName
Takes one parameter, FieldBase
CloudFlare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services
Takes two parameters, Source , Search
Takes one parameter, FieldName
Takes two parameters, Source, Search
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 three parameters Method, URL, Body
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.
A type of Prefix which allows the programmer to create Remarks or Comments in their code.