Search Results for perform

 

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.

 

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.

 

Session

Takes two parameters, Name, Value

 

CsvStreamWS

Takes two parameters, CSVData, bNoHeaders

 

SkipCalls

Takes no parameters

 

Geo

Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld

 

Folders

Takes a single variable, the relative path to the directory from root of project

 

Files

Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld

 

Plus8Encode$

Takes one parameter, Source

 

TabStream$

Takes one parameter, bNoHeaders

 

NulStream$

Takes one parameter, bNoHeader

 

Plus8Decode$

Takes one parameter, Source

 

Raw

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

 

CopyTable

Takes four parameters, DestinationTable, SourceTable, bWithParents, bWithPWHashes

 

HtmlButton

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

 

HtmlErr

Takes one parameter, ErrMsg

 

KeepIfFound

Takes 3 parameters, FieldBase, Fields, SearchTerms

 

TabStreamWS

Takes two parameters, CSVData, bNoHeaders

 

SaveTabFile

Takes two parameters, FileName, bUseHeader

 

SaveCsvFile

Takes two parameters, FilePath, bUseHeader

 

Text

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

 

WithGroup

Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld

 

WithAll

Takes five parameters, FieldBase, Destination, Action, Source, IfLenFld

 

Time

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

 

MergeRecords

Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks

 

LoadTabFileWS

Takes two parameters, FileName, bHasHeader

 

LoadCsvFileWS

Takes two parameters, FileName, bHasHeader

 

NulStream

Takes two parameters, Data, bHasHeader

 

Plus8Encode

Takes three parameters, FieldBase, Fields, IfLenFld

 

Plus8Decode

Takes three parameters, FieldBase, Fields, IfLenFld

 

ParseRecords

Takes two parameters, WorkFieldBase + FieldToParse, Delimiter

 

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.

 

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.

 

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.

 

Function

A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.

 

Folder

Takes two parameters, FolderPath, Action

 

File

Takes 3 parameters, Destination, Action, Source

 

 

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.

 

Get Started with Service Setup on a Server

A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.

 

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.Build , or when troubleshooting server errors.

 

[L] Lookup (DB Field Attribute)

Takes one parameter.

 

 

CsvStream$

Takes one parameter bNoHeaders and returns the result to an assigned variable

 

[L] Lookup (Top Query)

Takes one parameter.

 

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.

 

LTrimAny$

Takes two parameters, Source, Search

 

Json$

Has two parameters: Source, Name

 

Http$

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

 

Return

Takes a variable number of parameters.

 

OnError (Continue)

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

 

IncrKillCount

Has one parameter.

 

Cloudflared Tunnel

Cloudflared Tunnel exposes applications running on your local web server on any network with an internet connection with an outbound tunnel that connects directly to Cloudflare's edge network without the need to configure inbound firewall rules.

 

Try / Catch / Finally / End Try

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

 

SetKillCount

Takes one parameter, Value