Takes two parameters, PathToFile, Options
Takes two parameters, FileName, bHasHeader
Takes two parameters, FileName, bHasHeader
Takes two parameters, FileName, bHasHeader
Takes two parameters, CSVData, bNoHeaders
Takes two parameters, CSVData, bNoHeaders
Takes two parameters, FileName, bHasHeader
Takes two parameters, Data, Options
Takes two parameters, CSVData, bNoHeaders
Takes two parameters, Data, bHasHeader
Takes one parameter, Data
Takes two parameters, [WorkWith]+Scope, EmbedScope
Takes two parameters, FileName, bHasHeader
Takes two parameters, FileName, bHasHeader
Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld
Takes two parameters, Data, bHasHeader
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.
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.
A Remote Method may be called by any other Moxie system. It can be used to divide up a large system among a number of backend servers, or as a public API for 3rd parties. In order to call a Remote Method from MOX, the Remote statement is used.
A PaaS Method may be called by any other Moxie system. In order to call a PaaS Method from MOX, the PaaS statement is used.
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 two parameters, FileName, bHasHeader
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.
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.
Takes two parameters, Source and Match
Takes two parameters, Source and Match
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes two parameters, Source and Match
Has two parameters: Source, Name
Has one parameter, Options
Takes two parameters, Source and Match