Local Equinox tasks are only usable from form methods or application methods, outside subtable blocks. Remote Equinox tasks can be started from anywhere. External tasks are run from anywhere using one of the following:

• Command
• Shell
• System
• Task

This statement either runs a specified Equinox task, for example a form or report, or an external program. Equinox tasks may be run locally (in the currently executing client) or remotely (in another client on the local machine or in a client running on the server). The statement ExecuteSetRemote configures a task to run remotely. Tasks do not run remotely on single-user copies of Equinox; however applications can be configured to run single or multi-user without change if required.

The first argument, TaskName, describes the type of task to execute.

FileExpression is a string and identifies the specific task file name (if required). If you do not specify a path for the file, then Equinox will search for the file. The search process used depends on the type of file specified.

For Equinox parameter files, Equinox will start in the dictionary directory (below the PARAMS directory). If the file is another directory, then you must include the relevant path.

For non-Equinox files, Equinox searches the following directories (in the specified order): the current directory, the Windows and Windows system directories (for Windows installations only), the Equinox directory and any other directories in the system PATH variable.

The following table describes the values that TaskName (and FileExpression) can take, and whether the task can run remotely:

If the task was external, on Win32 environments SysReply contains the value of GetLastError if an error occurred, otherwise the handle from CreateProcess.

Note that if you use the Execute statement to run a local task in a method attached to a form, control does not return to the method. The form is reloaded from scratch after the task is completed. This means that the statement cannot execute while a record is being inserted or edited. Also note that you cannot run a local task in the At Start of Task or At End of Task methods on a form. A compilation error will occur.

The following new commands are available:

• CorrectMirror
• CorrectAllMirrors
• VerifyMirrorTable
• CorrectMirrorTable

These commands check the Equinox records in the database tables or table specified against the mirror version, and if required, the "Correct" versions correct the mirror data. If a priority of 3 (low priority) is specified in the preceding ExecuteSetMode statement and the ECC is available (client-server), the task is added to the ECC table list for processing in the background by the server. For example:

ExecuteSetMode -1,,, 3
Execute CorrectMirrorTable Orders

Otherwise the task runs in the foreground as specified by the remaining ExecuteMode parameters, as normal.

The following statements affect mirror operations but are not part of the ECC:

• MirrorDisable
• MirrorVerifyRecord

This example executes an export called endmonth. Note that the full file path has been included.

Execute Export "c:\Equinox\MyApp\params\accounts\endmonth.exp"

It was not actually necessary to provide the full file path, as the file was stored in the dictionary directory. The statement could have been written as follows:

Execute Export "endmonth"

The next example executes a batch file (in the background).

Execute Task "c:\batch\cbackup c: a:"

The last example executes a report called invoice. The file path information is stored in a local workarea.

Execute Report ReportFiles & "invoice.rep"

The last example executes a query remotely.

ExecuteSetMode
Execute Query "NewCust"