Takes two parameters, Source, Search
Takes one parameter, TableName
Takes no parameters
Takes two parameters, Source , Search
Takes two parameters, Source , Search
Takes two parameters, Source, Search
Takes four parameters, FieldBase, Destination, Source, IfLenFld
This is our current Terms of Service, last updated 2016-01-12.
This is our current Privacy Policy, last updated 2016-01-12.
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
Takes one parameter.
Takes one parameter, QueryName
The Setup Table controls aspects that can be changed while the server is running, and is intended to contain both Moxie.Build specific values as well as application specific.
Takes three parameters Method, URL, Body
Parameter is a space separated list of fields to choose from
Some Work Query command parameters can accept a source of either a Work Query Field name or a text literal. Text literals in these cases are prefixed with a backtick ` character.
Takes one parameter, a comma separated list of FieldNames
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 one parameter
[Col] takes one parameter
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".
This style guide provides comprehensive standards for writing clean, maintainable, and consistent MOX code for Moxie.Build. Code examples on this page are for illustrative purposes and are only intended to demonstrate style conventions.
Takes a single parameter, a QueryName
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
Takes a single Field name to test if it is true, with an optional Not operator to test if false, followed by the conditional statement
A Public Method may be called from any other Procedure, by the Default plug-in as part of the CMS.
Takes one parameter, the URL to purge from CloudFlare's cache
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc..]
Takes 3 parameters, Folder, Filter, bShowImgSize, bShowAccessed
Takes no parameters
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes a variable number of parameters
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, FileName, Options
Takes two parameters, [WorkWith]+Scope, EmbedScope
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes two parameters, Source, Values
Takes two parameters Command, Options
Takes two parameters, Source, Value
Has one parameter, Options
Takes one parameter, Source
Takes three parameters, FilePath, Start, Len
Takes two parameters, TableName, IfLenFld
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes two parameters, Source, MaxLength
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
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.
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.
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.
Prerequisites: This tutorial assumes that you have already learned about Managing Files .
Moxie.Build Keeps it Simple
The full stack in one app, delivered by one company.
Coding with the MOX server side scripting language is concise, well structured, and keeps your focus on the data. Use Moxie.Build in your company to pull together resources, centralize data, customize business workflows, and act as a highly accessible web portal for staff and customers alike.
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 a Category and Procedure if necessary. This page covers some of the basics that are involved in Front End development using the MOX language.
Upgrade Notes
In order to Upgrade an existing copy of Moxie.Build V4 or V5 to the most recent version of V5, you can use the Upgrade example files found in the Tools folder to help automate upgrading multi-service systems, or you can just replace the following files/folders:
Moxie.exe
Moxie.dll
Default.dll
/DBStore/BuiltIn.*
/Lib
/Public/BuiltIn
/Templates/Admin
/Templates/Clean
/Templates/Default
/Templates/Default5
/Templates/Report
The following video demonstrates how to download Moxie.Build to your workstation, and run it on localhost.
This video demonstrates how to get started with Moxie.Build with basic customization.