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.
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.
Takes two parameters, TableName, RecordAlias
Takes 1 Parameter which is the Table name that you want to count the Attached Records in. The specified Table must be a Child of the calling Record's Table.
Parameter is the table and field name that you want to sum in the form of TableName.FieldName. The specified Table must be a Child of the calling Record.
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes one parameter, QuantityToAdd
Takes two parameters, WorkFieldBase + FieldToParse, Delimiter
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.
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.
Takes two parameters, DBTableName, DBTableRecordAlias
Web/API Development Platform with an in-memory database, native-code CMS, and a powerful runtime environment Whether you are a new startup taking off or optimizing your business model for growth, Moxie.Build provides a robust platform with a proven track record for marketplaces, eCommerce, and business process automation
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc...]
Takes two parameters, FieldBase, FieldNames
Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld
Takes no parameters
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc..]
Takes two parameters, FieldBase, FieldNamesList
Takes no parameters
Takes 4 parameters, FieldBase, Left, Comparison, Right
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
Takes two parameters, FromIndex, ToIndex
Takes two parameters, CSVData, bNoHeaders
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes three parameters, TableName, SearchTerms, SearchInFields
Takes three parameters, TableName, Alias, Password
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes one parameter, TableName
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes two parameters, TableName, IfLenFld
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Takes four parameters, TableName, Relation, OtherTableName, IfLenFld
Takes two parameters, CSVData, bNoHeaders
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes two parameters, TableName, IfLenFld
Takes two parameters, Name, Value
Takes two parameters, Name, Value
Takes two parameters, TableName, IfLenFld
Takes no parameters
Takes no parameters
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes two parameters, CSVData, bNoHeaders
Takes five parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes two parameters, FieldName, Value
Takes two parameters, Data, bHasHeader
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes two parameters, Location, Mode
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes two parameters, [WorkWith]+Scope, EmbedScope
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Has no parameters.
Takes one parameter, Data
Takes two parameters, FileName, bHasHeader
Takes two parameters, FileName, bHasHeader
Takes two parameters, FieldBase, FieldNames
Takes two parameters, FileName, bHasHeader
Takes no parameters
Takes one parameter, FieldName
Takes two parameters, FileName, bHasHeader
Takes two parameters, FileName, bHasHeader
Takes two parameters, FileName, bUseHeader
Takes two parameters, FileName, Options
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes two parameters, FileName, bUseHeaders
Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld
Takes two parameters, Data, bHasHeader
Takes no parameters.
Takes two parameters, FieldBase, PivotField
Takes two parameters, TableName, IfLenFld
Has no parameters
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes one parameter, a Label
Takes four parameters, DestinationQuery, SourceQuery, UniqueField, UniqueValue
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.
In this example, you will see how to use a public method that works on or with the current WorkQuery that you pass into the method.
Takes two parameters, DestinationQuery, SourceQuery
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
A traditional way to check for hard errors and enable those errors to error softly.
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes one parameter.
Has one parameter, a Content.Lang prefix
Takes six parameters, DestQuery, SourceQuery, DestDestFld, DestXFld, DestYFld, SourceYFld
Used as a scoping keyword, similar to WorkWith/End WorkWith .
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.
Parameter is a space separated list of field names to be displayed when the user is viewing results from the Search List in the Admin interface.
Parameter is a space separated list of field names to have the display table sorted by when displaying search results in the Admin interface.
Takes one parameter.
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.
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.
Parameter is a space separated list of field names to be displayed.
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.
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.
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.
Has no parameters.
Accepts a space separated list of field names.
Has no parameters
Takes three parameters, ServerName, Port, bSecure, Send
Takes two parameters, Location, Mode
Takes two parameters, Title, Path
Takes one parameter, Name
Takes three parameters, TableName, Alias, Password
Takes one parameter, a top query destination variable
Takes one parameter, a List of possible group types
Takes one parameter, TableName
Takes two parameters, TableName and a boolean expression
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes one parameter, the name of a database table
Takes two parameters, ChildTableName, Mode
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Has no parameters
Takes two parameters, ChildTableName, Mode
Takes three parameters Method, URL, Body
Has no params
Has no params
Has no parameters
Takes no parameters.
Takes one parameter, TestCondition
Has no parameters
Takes one parameter, TableName
Takes one parameter, in the form of: Table|{Alias}|Field
Takes one parameter, bNoHeader
Takes one parameter, Index
Takes one parameter, TableName
Takes five parameters, Lat1, Long1, Lat2, Long2, Options
Takes no parameters
Has one parameter, Options