ProvideX V8.20 > Language Reference > 9. Special Command Tags

798

prog;function Parameters for the [tag]. For instance, for [DDE] to export to

Excel, you can open a worksheet using either,

"[WDX][DDE]EXCEL;existing_worksheet.WK1" or

"[WDX][DDE]EXCEL;"

In the first example, where a spreadsheet name is included, it

must exist on the client PC.

tag

ProvideX special command file tag. (All are listed in this chapter);

e.g., [DDE], [DLL], etc.

settings$

Serial device's attributes (baud rate, etc.). String expression.

statement

Command supported by ProvideX (some are not) for use with

EXECUTE or INVOKE + the [WDX] tag in WindX. String expression.

Subprogram for the CALL directive.

subprog

Note: This feature requires a WindX activation. Refer to the ProvideX website for

licensing information.

Description

The [WDX] tag is used as a prefix to perform an action on a remote client machine (if

your given command could be used on either client or server, and if the command

supports using [WDX]). The [WDX] tag can only be used in specialty commands when

running under WindX in a client-server environment.

WindX supports the use of the following commands via the [WDX] tag: SERIAL,

KEYED, DIRECT, SORT, PROGRAM, DIRECTORY, REFILE, LOCK, UNLOCK,

MNEMONIC and ERASE.

Note: If you are running an earlier version of ProvideX on a WindX PC, you must

encapsulate these commands in an EXECUTE "[WDX]..." or design your applications

to run on the remote site. Also, the DIR= option and the PURGE, FILE and INDEXED

directives are not supported by WindX and must be encapsulated in an EXECUTE etc.

To Detect WindX

To detect whether or not you're actually working on a WindX PC in Command mode, look

for the special prompt -} ... i.e., a hyphen with curly brace. In your applications, a test for

one of the following indicators will tell you that your session is running under WindX:

DEC(MID(MSE, 22,1))>0

TCB(88)<>0

For more information, refer to the TCB( ) Function, p.532, and the MSE System

Variable, p.563.

You can create a global variable in your WindX setup, and use it later to test for the

presence of a WindX client PC connection; then, if WindX is running the session, you

can use the [WDX] tag. In the following example, the user-defined variable %WDX

below is only set when WindX is running, otherwise its value is null:

IF MID(MSE,22,1)>$00$ AND MID(MSE,22,1)<$FF$ THEN %WDX$="[WDX]"