Search Results for request

 

Get Started with Development Examples

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.

 

Tcp$

Takes three parameters, ServerName, Port, bSecure, Send

 

HtmlHistory

Takes two parameters, Title, Path

 

HttpCookie

Takes 6 parameters, Name, Value, Path, Domain, Expires, Other

 

HttpSoap$

Takes 8 parameters, ServerName, Port, bSecure, Path, ExtraHttpHeaders, Envelope, ExtraBody, xml

 

WorkIf

Takes one parameter, FieldName

 

Http$

Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, [ContentType], [extraHeader], [body], [rtnHeaders]

 

SaveHttpFile

Takes two parameters, FileName, URL

 

Raw

Takes one parameter, the contents of which are used for the HTTP Reply Body

 

Pull

Takes three parameters, QueryName, FieldBase, FieldNames

 

Text

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

 

Value

Takes four parameters, FieldBase, Destination, Function, IfLenFld

 

Parse

Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld

 

LoadTableFields

Takes one parameter, TableName

 

ETableStream

Takes two parameters, ExcelTableData, Options

 

Num

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

 

[Pull] List of Fields from another Query

Takes up to three parameters, QueryName, FieldBase, FieldNames

 

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.

 

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.

 

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.

 

 

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.

 

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.

 

[Ensure] Field Exists

Takes a variable number of parameters, a comma separated list of TopQuery variable names

 

Foreign

Takes a single parameter, a QueryName

 

LangWith

Has one parameter, a Content.Lang prefix

 

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.

 

Remote Method

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.

 

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.