Search Results for error

 

Error

Takes one parameter, the text of the error to throw.

 

OnError (Continue)

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

 

[State] Error State

Takes one parameter.

 

FailIfRecError

Has no parameters

 

[AnyRecError]

Takes no parameters.

 

 

Folder and File Structure

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.

 

Try / Catch / Finally / End Try

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

 

[!] Limited Selection List

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.

 

DetachWithDelete

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

 

PWHash$

Takes three parameters, TableName, Alias, Password

 

Login$

Takes three parameters, Login, Password, bRememberMe

 

Detach

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

 

Lang$

Takes one parameter, Source

 

DeleteTable

Takes one parameter, TableName

 

HtmlHistory

Takes two parameters, Title, Path

 

HtmlErr

Takes one parameter, ErrMsg

 

HtmlAlert

Takes three parameters, Location, ClassNames, AlertText

 

Delete

Takes two parameters, TableName and a boolean expression

 

Backfill

Has no parameters

 

Attach

Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld

 

Parse

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

 

Reset

Takes no parameters.

 

NameField

Takes three parameters, FieldBase, OldFieldName, NewFieldName

 

NewFields

Takes two parameters, FieldBase, FieldNames

 

Value

Takes four parameters, FieldBase, Destination, Function, IfLenFld

 

Lang

Takes four parameters, FieldBase, Destination, Source, IfLenFld

 

ResetFields

Takes two parameters, FieldBase, FieldNames

 

SSReference

A command to help build spreadsheets

 

KeepFor

Takes two parameters, FromIndex, ToIndex

 

New

Takes two parameters, TableName, IfLenFld

 

PWHash

Takes three parameters, TableName, Alias, Password

 

Get

Takes two parameters, TableName, IfLenFld

 

Login

Takes three parameters, Login, Password, bRememberMe

 

DeleteFields

Takes two parameters, FieldBase, FieldNameList

 

KeepFields

Takes two parameters, FieldBase, FieldNamesList

 

Update

Takes two parameters, TableName, IfLenFld

 

UpdateOrNew

Takes two parameters, TableName, IfLenFld

 

Http$

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

 

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.

 

Export and Import of Database Schema

ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.

 

Critical

Takes one parameter, the Name of the critical section

 

[Ensure] Field Exists

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

 

EmailErr

Takes two parameters, SubjectPrefix, EmailBody

 

 

Get Started with Setting up the Development Environment

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.

 

Licensing

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.

 

[Raw] Raw HTML

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

 

[Ajax]

Takes 3 parameters, Trigger, DestinationID, Path

 

GoTo

Takes one parameter, a Label

 

Nightly Management Utility

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

 

Moxie.cfg Config

The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running

 

[CountIf]

Takes one parameter, TestCondition

 

GeoDistance$

Takes five parameters, Lat1, Long1, Lat2, Long2, Options

 

[L] Lookup (Top Query)

Takes one parameter.

 

NewEComQuery

Takes one parameter, QueryName

 

IncrKillCount

Has one parameter.

 

SetKillCount

Takes one parameter, Value

 

Command Line with .mox file

A .mox file, with MOX code in it, can be run from the command line while a Moxie.Build system is not otherwise already running.

 

TRONLog

Takes one parameter, OutputText