PassingFieldsOrFileNames < Main

---+ Passing Fields or File Names

To pass FIELD(s):
<pre>PASS &lt;fieldname1&gt; FIELD 
PASS &lt;fieldname2&gt; FIELD 
RUN &lt;ScriptName&gt; $* </pre>

The "$*" allows "ScriptName" to receive all the PASSed parameters, in their PASSed order. To change the order of outbound PASSed parameters, use "$2 $1 $3 etc..." instead of the "$*" parameter.

If you need to pass a "$" as part of your scriptname (say for example, you want to pass "$APPXPATH/DDD/AAA/filename"), preceed the "$"s that are not used in parameter passing with a backslash. For example:
<pre>PASS \$APPXPATH/VV/AAA/filename FIELD </pre>

---

You can pass the fully qualified filename to an external program or script by using the PASS statement, such as:
<pre>PASS TAR CUSTOMER FILE </pre>

This is similar to passing a field except that "path/filename" is provided rather than the contents of the file. The external program or script can then open the file and access it as needed.

(Note: this does *not* pass the ".dat" suffix of the "path/filename".)

See <a href="InvokingWindowsShellFunctions" target="_blank">Invoking Windows Shell Functions</a> for information on running Windows commands from APPX.
---++ Comments:

_Read what other users have said about this page or add your own comments._
---

<br />%COMMENT%

This topic: Main > WebHome > DeveloperTips > RunningWindowsFunctionsFromAPPX > PassingFieldsOrFileNames
Topic revision: r2 - 2016-02-18 - JeanNeron