Takes one parameter, Type
Takes one parameter, Type
Takes two parameters: Username, GroupTypes
Takes one parameter, a List of possible group types
Takes no parameters
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
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.
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
A type of Prefix which allows the developer to separate blocks of code into organized, defined parts to help provide clarity of the logical block and add structure to the code.
Takes one parameter
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bUseContainer, bNotResponsive, bInverted, HtmlPre, HtmlApn
Has two parameters: Source, Options
Takes three parameters Method, URL, Body
Takes a variable number of conditional statements to compare against a single source
Takes two parameters, FileName, FileData
Takes a single string as parameter, which is then appended to each line in the code block.
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.
The optional Moxie.http file is read on server start and controls the default HTTP headers set for all requests.
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.
Has one parameter, Options
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes one parameter, TableName
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, FieldBase, FieldNameList
Takes one parameter, Source
Takes two parameters, Location, Mode
Takes one parameter, a top query destination variable
Takes two parameters, Location, Mode
Takes one parameter, the contents of which are used for the HTTP Reply Body
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes two parameters, name, value
Prerequisites: This tutorial assumes that you have already learned about Managing Files .
Markdown enables simple formatting of plain text via easy to remember conventions. This page will provide you with some pointers on what formatting options are available with "Moxie Flavored Markdown".
Takes 3 parameters, Event, DestinationID, Path
Accepts a numeric value as a parameter.
Takes no parameters
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.
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.
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.
Takes a variable number of conditional statements
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes one parameter, ProcedureName
Private Method contained within a given procedure.
Has no parameters
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.
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
Accepts 3 parameters, first is required, 2nd and 3rd are optional. A trailing optional expression after an = sign may also assign a value on the same line.
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.Build , or when troubleshooting server errors.
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.
An Include Procedure cannot be executed directly, the contents of its source code can only be Included into other Procedures using the Include command.