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.
Takes two parameters, User and Password
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.
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.
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 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.
Takes two parameters: Username, GroupTypes
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.
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 three parameters, TableName, Alias, Password
Takes three parameters, QueryName, FieldBase, FieldNames
Takes a variable number of conditional statements to compare against a single source
Takes three parameters, Login, Password, bRememberMe
Takes one parameter, a List of possible group types
Takes a single string as parameter, which is then appended to each line in the code block.
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running
Cloudflared Tunnel exposes applications running on your local web server on any network with an internet connection with an outbound tunnel that connects directly to Cloudflare's edge network without the need to configure inbound firewall rules.
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 one parameter
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 a variable number of parameters
Takes one parameter, Source
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
A traditional way to check for hard errors and enable those errors to error softly.
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, FieldBase, FieldNamesList
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes three parameters, TableName, Alias, Password
Takes two parameters, Name, Value
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Has no parameters.
Takes one parameter, the contents of which are used for the HTTP Reply Body
Takes one parameter, ErrMsg
Takes two parameters, Title, Path
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes three parameters, Login, Password, bRememberMe
Takes one parameter, SessionID
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes two parameters, ChildTableName, Mode
Takes two parameters, ChildTableName, Mode
Has no parameters.
Used as a scoping keyword, similar to WorkWith/End WorkWith .
Takes no parameters
This is our current Terms of Service, last updated 2016-01-12.
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.
Accepts a numeric value as a parameter.
Parameter is a space separated list of field names to have the display table sorted by when displaying search results in the Admin interface.
Has no parameters.
Has one parameter
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.
A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.
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.
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 space separated list of field names to be displayed.
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Takes four parameters, DestinationQuery, SourceQuery, UniqueField, UniqueValue
Takes two parameters, destinationQuery, sourceQuery
Takes one parameter, the text of the error to throw.
Takes one parameter, QueryName
Takes two parameters, Text, Title
Takes a variable number of conditional statements
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.
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 , or when troubleshooting server errors.
Accepts a space separated list of field names.
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.
Takes two parameters, DestinationQuery, SourceQuery
Effective Websites. Downtown Quality, Small Town Affordability.
A Remote Method may be called by any other Moxie system. It can be used to divide up a large system among a number of backend servers, or as a public API for 3rd parties. In order to call a Remote Method from MOX, the Remote statement is used.