Search Results for database

 

 

 

 

 

 

 

 

 

 

 

Home

Web Portals & Databases

 

[L] Lookup (Top Query)

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.

 

Record Action

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.

 

UpdateOrNew

A database command which takes two parameters, TableName, IfLenFld

 

Update

A database command which takes two parameters, TableName, IfLenFld

 

[AccKey] Keyboard Accelorator Key

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.

 

UpdateOrNewWithAttach

A database command which takes four parameters, TableName, Relation, OtherTableName, IfLenFld

 

Message Handler

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.

 

Table Action

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.

 

EmptyTable

Takes one parameter, the name of a database table

 

Simple To Do App with MEAN Stack Comparison

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.

 

[L] Lookup (DB Field Attribute)

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.

 

Backfill

Has no parameters

 

Attach

Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld

 

Delete

Takes two parameters, TableName and a boolean expression

 

LoadTable

Takes one parameter, TableName

 

DetachWithDelete

Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)

 

Detach

Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)

 

Lookup$

Takes one parameter, in the form of: Table|{Alias}|Field

 

RecoverHtml$

Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string

 

FieldDef$

Takes a single parameter, in the format of TableName.FieldName#Deff where Deff is one of: Label, Attr, Note, or DevNote

 

Lang$

Takes four parameters, FieldBase, Destination, Source, IfLenFld

 

RecoverHtmlObj$

Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string

 

TemplateCustom

Takes one parameter, TemplateData

 

AppendTable

Takes one parameter, TableName

 

Setup$

Takes one parameter, Name

 

HtmlHistory

Takes two parameters, Title, Path

 

NewRecords

Takes one parameter, QuantityToAdd

 

Plus8Encode

Takes three parameters, FieldBase, Fields, IfLenFld

 

LoadRawFile

Takes one parameter, FilePath

 

NameField

Takes three parameters, FieldBase, OldFieldName, NewFieldName

 

HtmlTable

Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags

 

NamesToLabels

Takes no parameters

 

Text

Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld

 

HtmlForm

Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod

 

PWHash

Takes three parameters, TableName, Alias, Password

 

Search

Takes three parameters, TableName, SearchTerms, SearchInFields

 

New

Takes two parameters, TableName, IfLenFld

 

NewWithAttach

Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld

 

UnloadTableFiles

Takes one parameter, TableName

 

KeepIfFound

Takes 3 parameters, FieldBase, Fields, SearchTerms

 

Session

Takes two parameters, Name, Value

 

SkipCalls

Takes no parameters

 

[Header] Raw HTML

Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.

 

[#] Format (DB Field Attribute)

Takes 1 parameter, a formatting mask

 

[Footer] Raw HTML

Accepts one parameter which is the raw HTML content to be placed in the form, below the Field's location.

 

[SearchFieldList]

Parameter is a space separated list of field names to be displayed when the user is viewing results from the Search List.

 

[MaxLen]

Accepts a numeric value as a parameter.

 

[!] Limited Selection List

Parameter is a comma separated list (without quotes) of the options made available to the user and 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 it 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.

 

Syntax and Builtin Values, Procedures and Code Documentation

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.

 

Overview for PHP Developers

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.

 

Learn More about Frontend Development

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.

 

[Date] (DB Field Attribute)

Has no parameters.

 

[D] Default Value

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.

 

[_#] Format if not blank (DB Field Attribute)

Takes 1 parameter, a formatting mask

 

 

FailIfRecError

Has no parameters

 

Table Report

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.

 

OnError (Continue)

Used as a scoping keyword, similar to WorkWith/End WorkWith .

 

Try / Catch / Finally / End Try

A traditional way to check for hard errors and enable those errors to error softly.

 

[AnyRecError]

Takes no parameters.

 

Record Report

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.

 

Public Method

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.