+---------------------------------+
|          @ ... SAY/GET          |
+---------------------------------+
@ <row, column>
        [SAY <expr1>
                [PICTURE <expC1>]
                [FUNCTION <fcodes1>]
                [COLOR SCHEME <expN1>
                |COLOR <color pair list1>]]
        [GET <var>
                [PICTURE <expC2>]
                [FUNCTION <fcodes2>]
                [DEFAULT <expr2>]
                [ENABLE | DISABLE]
                [MESSAGE <expC3>]
                [[OPEN]
                        WINDOW <window name>]
                [RANGE [<expr3>]
                        [, <expr4>]]
                [SIZE <expN2>, <expN3>]
                [VALID <expL1> | <expN4>
                        [ERROR <expC4>]]
                [WHEN <expL2>]
                [COLOR SCHEME <expN5>
                |COLOR <color pair list2>]]

-----------------------------------
Performs I/O at a specified row and column.
-----------------------------------

<row, column>
        Numeric coordinates (zero or greater) that specify where output will
appear.

SAY <expr1>
        <expr1> is evaluated and displayed starting at <row, column>.

PICTURE <expC1>
        Value of <expr1> is displayed according to <expC1>.

FUNCTION <fcodes1>
        Offers an alternate means of including editing function codes for @ ...
SAY/GET command output.

COLOR SCHEME <expN1>
| COLOR <color pair list1>
        Changes standard, enhanced or both color attributes for SAY fields.
The standard settings are used with the SAY portion of the @ command,
while enhanced determine the colors that will be used with the GET.

GET <var>
        Edits a memory variable, array element or database field.  Editing is
undertaken starting at <row, column> or at next screen position
following end of output generated by SAY clause.

PICTURE <expC2>
FUNCTION <fcodes2>
        Has same purpose as in SAY clause, except used to edit data entered in
response to a GET.

DEFAULT <expr2>
        Specifies a value that is placed in GET field when appending records to
a database.  The DEFAULT clause will only be in effect when a format
file is open.  <expr2> is automatically placed in the GET field.  If you
press return when positioned on a GET field with a DEFAULT value, the
value of the DEFAULT is assigned to the GET variable.  The value
contained in <expr2> must be of the same data type as the GET variable.
If SET CARRY is ON, any DEFAULTs are replaced by values that are carried
over.

ENABLE | DISABLE
        Allows or prevents access and change to a GET field.  ENABLEd and
DISABLEd colors are controlled by color pairs 6 and 10 of COLOR SCHEME 1
respectively.

MESSAGE <expC3>
        Displays <expC3> when cursor is positioned in associated GET field.
The message is displayed on the last line of the screen and temporarily
cancels any SET MESSAGE expression.

[OPEN] WINDOW <window name>
        Allows editing of a memo field in a pre-defined memo editing window.
If OPEN is included, memo editing window is opened by default.

RANGE [<expr3>] [,<expr4>]
        Specifies range of values in which input must lie. To override the
default range message use an ON READERROR routine.

SIZE <expN2>, <expN3>
        <expN2> specifies height of editing region in rows; <expN3> specifies
width in columns.

        By default, FoxPro creates a GET editing region that is one row high.
The length of the editing region is determined by the memory variable or
database field you are editing or a PICTURE clause if one is included.
Including the optional SIZE clause lets you create an editing region
that is more than one row high.  The height of the GET editing region in
rows is specified by <expN2>, the width in columns by <expN3>.  The size
of editing region you create may be larger or smaller than the size of
the memory variable or field you are editing.  The size of the editing
region and the inclusion of the GET PICTURE clause determines how
editing is done in the region.  If the GET PICTURE clause is not
included:

        If you edit a database field and the size of the editing region you
specify with the SIZE clause is greater than the size of the database
field, editing occurs in an area equal to the size of the database
field.

        If you edit a memory variable and the size of the editing region you
create is greater than the size of the memory variable, the memory
variable is edited in the entire GET editing region.  The size of the
memory variable may be increased to the size of the entire GET editing
region.

        If you edit a memory variable and the size of the editing region is
less than the size of the memory variable, you may edit the entire
memory variable by scrolling within the GET editing region.

        If the GET PICTURE clause is included:

        If the PICTURE is smaller than the size of the editing region, the
PICTURE clause takes precedence.  For example, if the PICTURE clause is
"AAA" (three alpha characters) and the SIZE clause is 2,10 (two rows
high and ten columns wide), you may edit the first three characters of
the memory variable or database field in the GET editing region.

        If the PICTURE is larger than the size of the editing region, you may
edit the entire memory variable or database field by scrolling within
the GET editing region.

VALID <expL1> | <expN4>
        Permits validation of screen input as part of @ ... GET command. The
VALID clause can greatly simplify screen input validation when used in
conjunction with a user-defined function.  If a user-defined function
(UDF) is called within a VALID clause, the UDF returns the value of a
logical or numeric data type.  When you attempt to exit the GET field,
the VALID expression is evaluated using the value of <var>.

        Unlike the RANGE check, the VALID check is always performed unless the
field is exited by pressing Esc.

        With Logical Expression
                If <expL1> is .T., input is considered correct and READ proceeds to
next field for input.  If .F., value entered is considered incorrect and
a message in an alert is displayed directing you to reenter data after
pressing Spacebar.  A custom error message may be specified in place of
the default by using the optional ERROR clause.  This VALID checking
process continues until <expL1> is true (.T.) or until you press Esc.

        With Numeric Expression
                Action performed depends on value returned by <expN4>.
                0       validation error:  cursor remains in same GET field.
                +       relative number of fields to advance before inputting next GET
field.
                -       relative number of fields to move back before inputting next GET
field.

ERROR <expC4>
        Default error message replaced with <expC4>.

WHEN <expL2>
        Allows or prohibits editing of GET fields based on result of specified
condition. <expL2> must evaluate to true (.T.) before the cursor can
move into the field for editing.  If the WHEN  clause is specified and