Takes two parameters, TableName, IfLenFld
Takes four parameters, TableName, Relation, OtherTableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Has no parameters
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Has no parameters.
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
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 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.
This is our current Terms of Service, last updated 2016-01-12.
This is our current Privacy Policy, last updated 2016-01-12.
Takes two parameters, Title, Path
Takes three parameters, Login, Password, bRememberMe
Takes one parameter, SlowWritePercent
Takes one parameter, Control
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
Takes three parameters Method, URL, Body
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes two parameters, Name, Value
Takes two parameters, Name, Value
Takes no parameters
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes 3 parameters, Folder, Filter, bShowImgSize, bShowAccessed
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Has no parameters
Takes two parameters, name, value
Takes three parameters, Login, Password, bRememberMe
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
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.
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.
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.
A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.
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.
Moxie.Build supports translating any user-facing text into multiple languages from a single database table. Procedures, templates, and database field metadata all share the same translation store, so a string written once is reusable everywhere.
Takes 3 parameters, Event, DestinationID, Path
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.
Has no parameters
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
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.
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
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.