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.
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.
Parameter is a space separated list of field names to be displayed.
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.
Parameter is a space separated list of field names to have the display table sorted by when displaying search results in the Admin interface.
Takes one parameter, TestCondition
Takes one parameter, a gregorian number
Takes three parameters, TableName, Alias, Password
Takes one parameter, a top query destination variable
Has one parameter, Options
Takes three parameters, Login, Password, bRememberMe
Takes two parameters, Text, Title
Takes a variable number of conditional statements
Takes a single parameter, a FieldBase
A traditional way to check for hard errors and enable those errors to error softly.
Takes a variable number of conditional statements to compare against a single source
Takes one parameter, QueryName
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, FieldName
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost
Takes two parameters, FromIndex, ToIndex
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
A command to help build spreadsheets
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes one parameter, TableName
Takes three parameters, Location, ClassNames, AlertText
Takes one parameter, ErrMsg
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, HtmlEscapedString, and returns the Unescaped Version of this string
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes one parameter, Name
Takes 6 parameters, Location, Mode, ActionPath, Name, Class, Prompt
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes a single parameter, a QueryName
This is our current Privacy Policy, last updated 2016-01-12.
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.
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.
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 a Category and Procedure if necessary. This page covers some of the basics that are involved in Front End development using the MOX language.
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.
Prerequisites: This page assumes that you have already set up your Moxie.Build server and logged in as an admin user. This page covers some of the basics that are involved in using the Content Management aspects of the Moxie.Build system.
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.
Takes one parameter, the text of the error to throw.
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.
Has no parameters
Takes one parameter, the text of the exception to throw.
Accepts a space separated list of field names.
Has no parameters.
Accepts a numeric value as a parameter.
Takes one parameter.
Accepts 3 parameters, first is required, 2nd and 3rd are optional. A trailing optional expression after an = sign may also assign a value on the same line.
Web/API Development Platform with an in-memory database, native-code CMS, and a powerful runtime environment Whether you are a new startup taking off or optimizing your business model for growth, Moxie.Build provides a robust platform with a proven track record for marketplaces, eCommerce, and business process automation