⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 commands.htm

📁 DataLoad v4[1].2汉化版 这是一个向oracle应用系统导入数据的一个软件
💻 HTM
字号:
<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>DataLoad V4 Users Guide</title>
<base target="_self">
<link rel="stylesheet" type="text/css" href="comstar.css">
</head>

<body>

<h1><font size="4"><b>DataLoad Commands</b></font></h1>
<p>A DataLoad command is essentially a macro representing special processing.
There are two types of command, although this is not necessarily apparent to the
DataLoad user. The majority of commands act as a user friendly alias for the
normal data or keystrokes that can be entered into a cell and these are
discussed in this section, however a number of specialised built-in commands are
also available and are discussed <a href="#Built-in Commands">below</a>. A
command is typically used to hide complex keystrokes behind a more user friendly
command name. For instance, to &quot;Save &amp; Proceed&quot; in the NCA
Applications the following keystroke combination is required:</p>
<p>\%A{DOWN 4}{ENTER}</p>
<p>Attempting to enter those keystrokes every time a Save &amp; Proceed is
required will make the DataLoad spreadsheet more unreadable and therefore harder
to understand and maintain, and the likelihood of mistakes also increases. A
much better approach is to register those keystrokes under a user friendly
command name. The Save &amp; Proceed keystrokes are normally defined as *SP.
This means that the command can be used multiple times in one load but it is
only defined in one place, thus that definition can be changed once rather than
every time the command is used in a sheet.</p>
<p>Prior to V4.1 all DataLoad commands were hardcoded into the software and no
changes could be made to command definitions. As of V4.1 commands can be edited,
added or deleted. The default commands are maintained in the file &quot;commands.dat&quot;,
which must be located in the same directory as dataload.exe. Command definitions
are also stored in the DataLoad spreadsheet files. This makes the spreadsheets
portable and any special commands you have created for a your load will still
work as you designed them on another user's PC.</p>
<p>V4.1 also introduced the concept of <em>command groups. </em>For every
DataLoad command there can be a number of different definitions, each belonging
to a different group. Different definitions are required where a load may be
used with multiple applications that have different access paths to the same
functionality. For instance, to Save &amp; Proceed in Oracle's 10SC (Smart
Client) Applications the following keystrokes are required:</p>
<p>\%AA</p>
<p>Because this is different to the NCA definition we may want to define *SP
differently in multiple command groups, thus allowing the same command to be
used to load into different applications but with different keystrokes
resulting. A command group must be selected from the drop down list on the main
DataLoad form before a load can commence.</p>
<p>The following table lists the standard DataLoad commands available and the
effects of using those commands.</p>
<p><font face="Wingdings">G</font> Many shortcuts used by NCA are different to
those in 10SC (Smart Client). For that reason many of these commands will not
work in 10SC when used in versions of DataLoad prior to V4.1. Before that
version the commands were configured for Oracle Applications NCA and sent the
appropriate keystrokes for that product. If Oracle Applications NCA is not the
DataLoad target and V4.1 or above cannot be used these commands may not work
because of different shortcut commands or menu structures. In this case direct
keystrokes should be sent, as described in <a href="keystrokes.htm" target="Main">Sending
Keystrokes</a>.&nbsp;</p>
<table border="1" cellpadding="7" width="600">
  <tr>
    <td valign="top" width="32%">
      <h3>DataLoad Command<br>
      (Case Sensitive)</h3>
    </td>
    <td valign="top" width="68%">
      <h3>Application Action(s)</h3>
    </td>
  </tr>
  <tr>
    <td valign="top" width="32%" height="4">&nbsp;</td>
    <td valign="top" width="68%" height="4">&nbsp;</td>
  </tr>
  <tr>
    <td valign="top" width="32%">TAB</td>
    <td valign="top" width="68%">&lt;Tab&gt;</td>
  </tr>
  <tr>
    <td valign="top" width="32%">ENT</td>
    <td valign="top" width="68%">&lt;Enter&gt;</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*UP</td>
    <td valign="top" width="68%">&lt;Up Arrow&gt;</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*DN</td>
    <td valign="top" width="68%">&lt;Down Arrow&gt;</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*LT</td>
    <td valign="top" width="68%">&lt;Left Arrow&gt;</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*RT</td>
    <td valign="top" width="68%">&lt;Right Arrow&gt;</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*SP</td>
    <td valign="top" width="68%">Save &amp; Proceed</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*FE</td>
    <td valign="top" width="68%">Field Editor</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*PB</td>
    <td valign="top" width="68%">Previous Block</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*NB</td>
    <td valign="top" width="68%">Next Block</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*PF</td>
    <td valign="top" width="68%">Previous Field</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*NF</td>
    <td valign="top" width="68%">Next Field</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*PR</td>
    <td valign="top" width="68%">Previous Record</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*NR</td>
    <td valign="top" width="68%">Next Record</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*ER</td>
    <td valign="top" width="68%">Erase Record</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*DR</td>
    <td valign="top" width="68%">Delete Record</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*FR</td>
    <td valign="top" width="68%">First Record</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*LR</td>
    <td valign="top" width="68%">Last Record</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*SAVE</td>
    <td valign="top" width="68%">Save Record</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*SB</td>
    <td valign="top" width="68%">Send a single space character</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*ST</td>
    <td valign="top" width="68%">Select entire field text.</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*SL<i>N</i> or *SL(<em>N</em>)</td>
    <td valign="top" width="68%">Pause for N seconds. <b>Note 1</b></td>
  </tr>
  <tr>
    <td valign="top" width="32%">*BM</td>
    <td valign="top" width="68%">Block Menu</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*A<i>X</i></td>
    <td valign="top" width="68%">Alt + X where X is a single letter (A-Z). <b>Note
      2</b></td>
  </tr>
  <tr>
    <td valign="top" width="32%">*FI</td>
    <td valign="top" width="68%">Find <b>+</b></td>
  </tr>
  <tr>
    <td valign="top" width="32%">*FA</td>
    <td valign="top" width="68%">Find All <b>+</b></td>
  </tr>
  <tr>
    <td valign="top" width="32%">*QE</td>
    <td valign="top" width="68%">Query Enter <b>+</b></td>
  </tr>
  <tr>
    <td valign="top" width="32%">*QR</td>
    <td valign="top" width="68%">Query Run <b>+</b></td>
  </tr>
  <tr>
    <td valign="top" width="32%">*CL</td>
    <td valign="top" width="68%">Clear Field <b>+</b></td>
  </tr>
  <tr>
    <td valign="top" width="32%">*IR</td>
    <td valign="top" width="68%">Insert record <b>+</b></td>
  </tr>
  <tr>
    <td valign="top" width="32%">*CW(<i>window</i>)</td>
    <td valign="top" width="68%">Change to window <i>window</i>. <b>+</b></td>
  </tr>
  <tr>
    <td>*ML(<em>coordinates</em>)</td>
    <td>Position the mouse at <em>coordinates</em> and press the left button. ++</td>
  </tr>
  <tr>
    <td>*MR(<em>coordinates</em>)</td>
    <td>Position the mouse at <em>coordinates</em> and press the right button.
      ++</td>
  </tr>
</table>
<p><b>+ </b>DataLoad V4.0.2 and above only.</p>
<p>++ DataLoad V4.1 and above only.</p>
<p><b>Note 1</b> DataLoad can send keystrokes to NCA faster than they can be
processed. If this problem is encountered delays can be added to the load which
will pause DataLoad at key times. The *SL<em>N</em> command can be added to the
input script to indicate DataLoad should 'sleep' for a given number of seconds.
E.g. '*SL5' will cause a delay in processing for 5 seconds. Decimal numbers can
be used for more precise delays, E.g. *SL0.5 will result in a half second delay.
A large number of predefined delays are available in DataLoad and these, along
with *SL, are described in greater detail in <a href="usingdelays1.htm" target="Main">Using
delays</a>. To reduce setup work, predefined delays should be used instead of
*SL wherever possible.</p>
<p><b>Note 2</b> In Oracle Applications it is sometimes necessary to press a
button to navigate to another block. This can be achieved by pressing
&lt;Alt-X&gt;, where X is the letter that is underlined on the button. Any menu
item can also be invoked by pressing &lt;Alt&gt; + the letter underlined on the
menu.</p>
<a name="Built-in Commands">
<h3>Built-in Commands</h3>
</a>
<p>The following commands are built-in to DataLoad and cannot be edited or
replaced in the commands form.</p>
<table border="1" cellpadding="7" width="600">
  <tr>
    <td valign="top" width="32%"><b>Command</b><br>
      <b>(Case Sensitive)</b></td>
    <td valign="top" width="68%"><b>Application Action(s)</b></td>
  </tr>
  <tr>
    <td valign="top" width="32%" height="4">&nbsp;</td>
    <td valign="top" width="68%" height="4">&nbsp;</td>
  </tr>
  <tr>
    <td valign="top" width="32%">*CW(<em>window</em>)</td>
    <td valign="top" width="68%">Make <em>window</em> the new target window for
      DataLoad.</td>
  </tr>
  <tr>
    <td>*SL<em>N</em> or *SL(<em>N</em>)</td>
    <td>Sleep for <em>N</em> seconds.</td>
  </tr>
  <tr>
    <td>*ML(<em>coordinates</em>)</td>
    <td>Position the mouse at <em>coordinates</em> and press the left button.</td>
  </tr>
  <tr>
    <td>*MR(<em>coordinates</em>)</td>
    <td>Position the mouse at <em>coordinates</em> and press the right button.</td>
  </tr>
</table>
<p><strong>*CW</strong> allows you to switch between different windows and load
data into all of them. This command is useful when it is not possible to change
windows by any other means, but also has good uses even when this is not the
case. It is often possible to change the active window through the application,
for instance navigating to the next block in Oracle Applications sometimes
causes the focus to move to another window. Despite this it is often faster to
change to the new window by calling *CW rather than allowing the application to
make the change, and this not only results in faster loads but reduces errors as
well.</p>
<p><strong>*SL</strong> causes DataLoad to 'sleep' for the specified number of
seconds and is an important command for controlling the rate at which DataLoad
progresses. This command is described in more detail in <a href="usingdelays1.htm" target="Main">Using
delays</a>.</p>
<p><strong>*ML and *MR</strong>. These commands will cause a left or right mouse
click to occur at the point on the screen specified in the coordinates
parameter. These commands can be very important and have a number of uses.
First, they are essential for accessing any application functionality for which
no keyboard shortcut exists. Where a button, for example, cannot be accessed
using a keyboard shortcut a mouse click must be used. The mouse is also very
useful for improving the speed and accuracy of navigation within the application
during a load. It is often much quicker to move the cursor using the mouse than
by issuing the necessary keystrokes. This may apply whether the cursor is just
moving between blocks in a form or between different windows.</p>
<p>The coordinates parameter is the X and Y screen positions where the click
should occur. Since there is no way a user can know what these coordinates are
DataLoad has a method for automatically inserting the coordinates into the
command. When the user enters *ML or *MR in a cell a dialog box is shown
prompting the user to position the mouse where the click should occur. This
dialog box should <em>not</em> be dismissed yet because doing so indicates to
DataLoad that the mouse is in the correct position for the click. When the mouse
is in the location where the click should occur the user should then press
Enter. This will dismiss the dialog box and insert the screen coordinates into
the *ML or *MR command. Those coordinates can be manually entered into further
cells where this same click should occur, or the dialog box can be displayed
again by entering *ML or *MR.</p>
<p>The mouse clicks work very well to make functionality available for which no
keyboard shortcuts exist, or to improve cursor navigation during a load. This
command is only suitable, however, where the item to be clicked will always be
in the same location. Since Oracle Applications' forms are always drawn in the
same position this should not be a problem, however it is important that the
forms are left in their default positions while the load is being developed and
the *ML and *MR commands programmed.</p>

</body>

</html>

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -