Web Portals & Databases
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 one parameter which is the keyboard key which will be used as the Access Key for a given Database Table's field.
*Note: By default, each Field's Access Key will be initialized to the first character of the Field's Label.
Parameter is the database path that is to be looked up in the form of TableName|Alias|FieldName where it may be a specific fixed path or you may use {} to replace one or more of the path components where the value inside the {} is a field name in the current record.
A database command which takes four parameters, TableName, Relation, OtherTableName, IfLenFld
A database command which takes two parameters, TableName, IfLenFld
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 database command which takes two parameters, TableName, IfLenFld
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.
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 one parameter, the name of a database table
Parameter is the database path that is to be looked up in the form of TableName|Alias|FieldName where it may be a specific fixed path or you may use {} to replace one or more of the path components where the value inside the {} is a field name in the current record.
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes two parameters, TableName and a boolean expression
Has no parameters
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes two parameters, Title, Path
Takes one parameter, Name
Takes one parameter, a top query destination variable
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes one parameter, TableName
Takes one parameter, in the form of: Table|{Alias}|Field
Takes one parameter, TemplateData
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes one parameter, QuantityToAdd
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes one parameter, FilePath
Takes three parameters, FieldBase, Fields, IfLenFld
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes no parameters
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes two parameters, TableName, IfLenFld
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes one parameter, TableName
Takes three parameters, TableName, Alias, Password
Takes no parameters
Takes one parameter, TableName
Takes three parameters, TableName, SearchTerms, SearchInFields
Takes two parameters, Name, Value
Takes a single parameter, in the format of TableName.FieldName#Deff where Deff is one of: Label, Attr, Note, or DevNote
Accepts one parameter which is the raw HTML content to be placed in the form, below the Field's location.
Has no parameters.
Takes 1 parameter, a formatting mask
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.
Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.
This hands-on experience article is written by an experienced PHP developer, and serves as an overview to help you understand the similarities and differences.
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.
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.
Parameter is a value or an expression to be used when a record is created if no value is specified during the creation. The value or expression is run through the Assignment Attribute in order to calculate it's result.
Takes 1 parameter, a formatting mask
Accepts a numeric value as a parameter.
Has no parameters
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.
Used as a scoping keyword, similar to WorkWith/End WorkWith .
Takes no parameters.
A traditional way to check for hard errors and enable those errors to error softly.
Has no parameters.
Parameter is a space separated list of field names to be displayed when the user is viewing results from the Search List.
Has no parameters
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.
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.