file or an expression (for calculated fields).

In _{this instance, the brackets {}} are to be _actually typed _{in the}

configuratiom contrary to the notation elsewhere _{in this} manual where

brackets are used _{only to signify optional} cormand e1«nents _{to the}

reader of the manual.

Format _{options for the} ENTRY command _are as follows:

F|INcTTnN SJLNIU

DECIMAL POINTS {P0INTS=n} where _{"n" is the} number _{of places to the}

right of the decimal _{point in the} window. _This can

reformat a window _or can be used _{to configure} an

integer-only numeric _field by _setting a _{value of zero} (O) _{for "n".}

————————— — ————

C-20 DATA ENTRY DataFlex 2.0 _User's Manual

~——— = ~——~——————

AUTOFIND* {AUTOFINCñ Executes a FIND EQuals on the main index _of which _{the data elment} on the EN7RY command _{line is} a

part.

If

the desired FIND _is on a multi-segment index, the AUTOFIND _should be on the last entry

command _{for the} segments _that make up the index, so

that all data necessary for FINDing has been _entered

prior to execution of the AUTOFIND. Record number may

not be _{part of the index of} which _the AUTOFINDing data element _is a part. Windows _for data from _related

files

will also be _{fi11e& provided there are} ENTRY connands _for those windows.

SKIP _IF FOUND* {SKIPFOUNCñ _Display data _{in the} window

if

a record is

FOUND _with key data matching _the data _{in the} wiñájwY and move _{the cursor to the next} window.

If

no such

record has been F0UNlj, _{leave cursor in} window and accept _{operator input.}

FIND REQUIRED* {FINDRECÜ _{Requires that} an active record be _{in the}

buffer before the operator can pass this window _{in the} image. The

cursor will rémaln in this window until a

successful FIND _{Is completed.} The BACKFIELD _Flex-key can move _{the cursor in reverse to} execute _the FIND on

another window. _{Pressing the} CLEAR _{Flex-key will}

return the cursor to the

first

wfndow on the image. UPPER CASE {CAPSLOCK) _{Converts all lower} case alpha _characters

entered in the window _to upper case.

REQUIRE ENTRY {RE(JLJJIRED} The _{cursor cannnot} be moved _{to the next} data _entry window _{until data} has been _{entered into the}

current window.

RANGE CHECK {RANGE = #L iC2} {RANGE.= _{nn/ddlyy. m/dd/yy} Provides} an automatic check of entered data and declares an

error and _{returns the cursor to the} window

if

the date or numeric _{value entered} does _not

_fall

within the specifications in the comand. The

_first

_{value is the} low end _{of the} rangep and _the second _{is the} high end. The upper and _{lower values in the} comand are included within the valid range. Literal numbers and dates can be used. _Variables may not be used.

VALIDITY MECK _{{mECK="entryl|entry2|entryn"}{MECK=string_var}}

Provides an automatic check _{of entered} data and

declares an _error and _{returns the cursor to the} window

if

the entry does _not match any substring in the aiux comand. Where an eligible entry has _{fewer characters}

than the window9 _the excess characters must be _speci-

fied as spaces (shown below _as 16). The _vertical bars

(I) shown below are recomended _{optional delimiters.}

De1imitersp

_if

úSéd,r should be _{characters unlikely to} be _{input erroneously} by _operators. The connand may

alternatively reference a previously-defined in-memory

string variable (not a window _or database _element): {MEa(="YEslNoBlYBBlNBB"}

"————————————————————

"

DataFlex 2.0 _User's Manual DATA ENTRY C-21

FORCE PUT {FORCEPUT} _Puts data _{in the} windows _{to the record}

buffer regardless of whether any data has been changed from _{that originally displayed.} Norma11yg _{a put will}

not occur unless some data has been changed. DO NOT PUT DATA {NOPUT} Do _{not put} data from _the window _{into the}

record buffer. This protects data from being changed by _{the operator.}

NO DATA ENTRY {NOENTER} Data from _the found _{record is displayech} but

the cursor skips the wiñdowo _{preventing entry.} NOENTER _{skips the} window even

_if

no record is found, unlike SKIPFOUND (see _above).

DISPLAY ONLY {DISPLAY0NLY} Combination _of NOFUT and NOENTER above. Data _{is not} moved from _the window _{into the record}

buffer, and _{the cursor skips the} window.

RETAIN DISPLAY {RETAIN} _{Maintain the} data _in window even

if

a CLEAR command _{is execute6 but clear the} window

_if

two

successive CLEARs are keyed.

RETAIN ALWAYS {RETAINALL} _Maintain data _in window _{at all times;} never clear.

* The cotmands _{with asterisks} are all FINDing comandm and may be used _only on windows relating to indexed database elements (see the

chapter on "Designing Databases" _for more information on indexing).

The command _options, and _{the formatting options} above can all be used

cumulatively on an ENTRY command _line:

EN1RY

_file.field

page.5 {AUTOFIND,SKIPFOUND,CAPSL0CK}

The maximum _{length of} any DataFlex comnand _{line is} 255 _characters.

Multiple options on an ENTRY command _line are all enclosed _within the brace _characters {braces}, separated by comas (,)¿

A _special form _{of the} ENTRY command _is used where _expressions are to

be _displayed. The _default mode _{of the} window becomes _{display only} when _{this format is} used.

FORMAT:

ENTRY _(expression) w1ndow_arg EXAMPLE:

ENTRY _{(date_today+30) screen.5} ENTRY AND AUTOPAGE

The ENTRY command can be used _{without specific reference to} image windows by _using the-AUTOPAGE command. (AUTOPAGE _{functions automati-}

cally in the ENTER _{macro for the}

_first

screen imagep and needs _to be

explicitly written only

_if

there are two or more screens.) AUTOPAGE ———————————— ——————— ____=~_=~~~~>=————

C-22 DATA ENTRY DataF1ex 2.0 _User°s Manual

sequentially

_(left

to right9 starting witht the top line and _working down) accesses _the windows _{of the} screen image named as the argument

of the command (see _{the section of this} manual on Direct Control of

Data _Entry), and _{permits the} window _{references to} be

_left

_off. NOTE: The ENTRY command can ONLY by used _{within the} ENTRY _{section of}

the ENTER macro or within the ENTERGROUP command.

Since ENTER _{is internally} composed _of a set of subroutines, a RETURN command _{is required to terminate the} ENTRY _{section of the configura-}

tion.

If

you don't need any of the user-defined procedures _{or post-entry}

processing, you may simply end the ENTER configuration with an ENTEREND.

The _next page illustrates a totally straightforward, unimaginativeg yet efficient ENTER _{configuratiom}

_It

makes use of the AUTOPAGE

function, so page window _{references are not} necessary.

_It

has _{all of}

the components _of an ENTER configuration: 1. A _labeled image

2. An OPEN command _{with filename} argument

3. An ENTER command _{with filename} argument

4. ENTRY commands _with data element arguments

5. ENTRY commands _terminated by a RETURN

6. An ENTEREND command _to end _{the configuration}

~

DataFlex 2.0 _User's Manual DATA ENTRY C-23 ="=———___—~—

——————— EXAMPLE FORMAT FOR ENTER

/LIST My _{Mailin' List} Name: Address: City: State:

_

ZIP:

l*

// --

pre-enter

_--

OPEN MAIL

_//

open data

_file

ENTER MAIL _'

_//

_{start enter} macro

// --

begfning of entry section

_--

AUTOPAGE LIST

_//

_{sequentially assign} windows

//

not actually required in this

//

single-screen configuration

ENTRY MAIL.NAME {AUTOFIND} ENTRY MAIL.ADDRESS

EN1RY MAIL.CITY

EN1RY MAIL.STATE {CAPSLOCK} ENTRY MAIL.ZIP

RETURN

_//

end _{of entry section}

//

not actually required since next

//

command _is enterend ENTEREND

_//

end _{of enter} macro

———————

C-24 DATA ENTRY _DataFlex 2.0 _User's Manual ——————

THE USER-DEFINED PROCEDURES

Many ENTER _{configurations}

_will

need _{to perform} updates _{in related}

files,

have _{error checking or delete protection built im etc.} These

operations are accommodated by _{five user-defined} procedures which are

automatically executed when _{the corresponding DataFlex Flex-key is} pressed _{during the execution of the} ENTER _{configuration.} The _User-

Defined procedures _are:

ENTER.SAVE: executed on a SAVE command ENTER.DELETE: executed on a DELETE command

ENTER.EDIT: executed _on an EDIT and on a DELETE command ENTER.CLEAR: executed _on a CLEAR command

ENTER.EXIT: executed on an EXIT command

These _{ljser-Oefined} procedures _{are automatically called} by _the ENTER command macrog but they are functiona11y no different from any other labeled DataFlex sub-routine called by _your own GOSUB _comands. The

inclusion of the colon ":

_"

at the end _{of the} procedure name is

required to identify them as labels; om!tting the colon will cause an

error.

If

an ERROR _{is declared within} any of the procedures the associated

function

_will

be _disabled.

The ENTER.SAVE procedure _is executed whenever a new record is created or an existing reccmi _{is edited.}

The ENTER.DELETE procedure _is executed whenever an existing record is deleted.

The ENTER.EDIT procedure _is executed whenever an existing record is deleted OR an existing record is edited. This works _{well with the} save procedure _to keep _{the consistency of counters} and _{totals in} a

related

_file.

The ENTER.CLEAR procedure _is executed whenever _the CLEAR _{Flex-key is}

pressed.

The ENTER.EXIT procedure _is executed whenever _the escape key _is

_hit

and _{is primarily intended to allow conditional disabling of the} escape key by _{declaration of} an _error.

Each _{of the User-Defined} procedures must be _{ind1vidua1ly terminated}

with the use of a RETURN command (see _the example on the next page).

DataFlex 2.0 _User's Manual DATA ENTRY C-25

The _{configuration} below _{illustrates the} use of the ENTER.SAVE and ENTER.EDIT _procedurem which are executed _{every time} a record is saved and _{edited/deleteck respectively.} An _{application requirement for} a

mailing

_list

uses only one

_file

for the

_list

information. However,

it

is desired to maintain an on-line counter of how many _{records are in}

the

_file.

To do _this we

_will

establish a field in the system

_file

(SYSFILE.COUNTER) _{that contains the} number _{of records in this}

_file.

To _{maintain the count correct1y? the counter} must be incremented when a record is created; when a record is dejete6 the counter must be decrementéd» and when an edit is donep _{the counter} must be

_left

unchanged. /LIST My _{Mai1in' List} Name: Address: City: ST:

_

ZIP:

l*

//

only those parts of this example _that are changed have comments OPEN MAIL

OPEN SYSFILE

_//

open other

_file.

ENTER MAIL AUTOPAGE LIST

ENTRY MAIL.NAME {AUTOFIND) ENTRY MAIL.ADDRESS

ENTRY MAIL.CITY

ENTRY MAIL.ST {CAPSLOCXJ ENTRY MAIL.ZIP

RETURN

//

The ENTER.SAVE procedure _will execute whenever a record is saved.

//

When a record is createcb only this procedure _is executed,

//

incrementing the counter.

ENTER.SAVE: CALC (SYSFILE.COUNTER+1) TO SYSFILE.COUNTER SAVE SYSFILE

RETURN

_//

_return from save procedure

//

The ENTER.EDIT procedure _is executed whenever a record is deleted

//

or edited. For a delet1om

it

decrements the counter.

It

also

//

decrements _{the counter in} an edit, but true edits are followed by

//

SAVEm which execute ENTER.SAVE, _{offsetting the} decrement _{to zero.} ENTER.EDIT: CALC (SYSFILE.COUNTER-I) TO SYSFILE.COUNTER

SAVE SYSFILE

RETURN

_//

_return from _delete procedure ENTEREND

C-26 DATA ENTRY _DataFlex 2.0 _User's Manual

ENTDISPLAY Command

The ENTDISPLAY comand causes all ENTRY data _{elments for the} data

file

named _{in the} argument _{to display} on _{the screen,} along with all

those in other related

_files.

Its apparent effect is exactly as though _the SUPERFINO _Flex-key had been pressed by _{the operator.}

_It

may be used _{in the} ENTRY _{section of an} ENTER _or ENTERGROUP _configura-

tion and/or in a KEYPROC _{(for the} FIND key, _{for example).} FORMAT:

ENTDISPLAY <df_ff1ename>

Where <df ff1ename> _{is the} name of the data

_file

from _in which

the displayed record is to be _found. EXAMPLE:

FIND GE mail BY INDEX.I ENTDISPLAY _mail

ENTDISPLAY would be used, _for examp1eg _in an alphabetic FIND such as

the one in the configuration above which _is done _{with the} AUTOFIND

option on the ENTRY MAIL.NAME _line.

_{If it}

_{is desired,} however, _to do a FIND _greater than or equal _{to (frequently desirable} when _the FIND

target's spelling is not _exactly known), _the AUTOFIND _{option wIll not}

allow this9 since

_it

only does _exact FIND _equals. For _{that, the}

following configuration would be _{appropriate (note the differences):}

/LIST My _{Mai1in' List} Name: Address: City: ST: _ZIP:

l*

//

only those _{parts of this} example _that are changed have connents

//

this configuration will always _{find a record} OPEN MAIL

ENTER MAIL AUTOPAGE LIST

ENTRY MAIL.NAME

_//

AUTOFIND removed _here

FIND GE MAIL.NAME

_//

FIND _greater than _or equal _to added here ENTDISPLAY MAIL

_//

ENTDISPLAY comand

ENTRY MAIL.ADDRESS ENTRY MAIL.CITY

ENTRY MAIL.ST {CAPSLOCK} ENTRY MAIL.ZIP

RETURN ENTEREND

Another use of ENTDISPLAY _{im in} a multiuser environment9 _after a REREAD command, _{to display the} REREAD _{record for inspection.}

DataFlex 2.0 _User's Manual DATA ENTRY C-27 =========——————————————————————

POST-ENTRY PROCESSING:

After the end _{of the User-Defined procedures, the} comand ENTEREND must be used _{to terminate the} ENTER macro. When _the escape key _is

pressed, the ENTEREND command

_will

_close out _the ENTER macro. At this point you may ABORT _{configuration,} (MAIN _{to another configuration, or} proceed _with any other sequence _{of DataFlex} commands.

ENTER _— SEQUENCE OF OPERATION:

An _{understanding of the order in} which _the ENTER macro executes

specific functions will aid in the development _of more complex

configurations. Steps _{that involve specific multiuser operations} are

Identified. DataFlex systems _in which _single-user mode was selected

(see SETSCREEn _{procedures) will not} perform these _multi-user

functions.

CREATING A NEW RECORD:

a) _Clear screen and _{clear record buffers.} b) _Operator

_fills

_{in the} data windows.

c) Operator hits the SAVE key _{or exits the last} image window. d) Record _is autcxnatica11y _locked and _{related records} are _re-

read from _the database _{(multi-user systans only).} e) Data _in data windows _is moved _{to record buffer(s)}

accwding tQ _the ENTRY cQnnands.

f) ENTER.SAVE procedure _is executed _(including any parts defined by _{the user).}

g) Records are ATTANed and SAVEd _{to disk.}

h) _{All records} are unlocked _(multi-user systems _only).

i) Screen and _{record buffers} are cleared for new entry.

EDITING AN EXISTING RECORD:

a) _{Clear screen} and _{clear record buffers.}

b) _Operator FINDS _{a record in the} main

_file

by any available

key.

C) Related _record(sb

if

any, are found and _displayed. d) _Operator changes data _{in window(s).}

e) _Operator SAVES _record.

f) Records are locked and ali _active records are re-read from disk (multi-user systans only).

g) ENTER.EDIT procedure _is executed _(including any parts defined by _{the user).}

h) Data _is moved from CHANGED data windows _{to record buffer.}

i) ENTER.SAVE procedure _is executed _(including any parts defined by _{the user).}

j)

Records are ATTAMed and SAVEd _{to the} data base. k) _{All records} are unlocked _{(multi-user systans only).}

I) Screen and _{record buffers} are CLEARed _for new entry.

C-28 DATA ENTRY _DataFlex 2.0 _User's Manual

DELETING A RECORD:

a) _Clear screen and _{clear record buffers.}

b) _Operator FINDS a record in the main

_file

by _any key.

c) Related record(sL

_if

any, _are found and displayed. d) _Operator presses the DELete RECord key.

e) Records _{are locked} and _all RELATED _records are _re-read from

the data base _(multi-user systems _only).

f) ENTER.DELETE procedure _is executed _(including any parts defined by _{the user).}

g) ENTER.EDIT _{procedure is} executed _(including any parts defined by _{the user).}

h) Record _in main

_file

_{is deleted.}

i) Related _{records are} saved.

j)

All records are unlocked (multi-user systans only).

k) Screen and _{record buffers are cleared for} new _entry. ENT$PERMISSIVE INDICATOR

The ENTER macro is designed _{to prevent errors of the sort} which _could

arise from _operator sequences such as the following:

a. Operator finds a record and one _or more related records by use of SUPERFINO _{(the display of} data from _{records in multiple}

files

related to each _{other is not necessarily apparent to the}

operator);

b. Places _{cursor in} a key _{field in} a related-to record; c. Presses FIND and FINDS another record in the related-to

file,

bringing

_it

into the record buffer with the earlier-

found _{relating record;} and

d. SAVES _{this combination of possibly-unrelated records} as though _they were related to each _other.

What _actually happens _{in this instance is that the} ENTER.EDIT

procedure _is executed _{on the} NEW _{record Instead of the} OLD one. This

makes _{the totals} and _{counters in} both _{the old} and new related-to

_files

incorrect.

This possibility is eliminated by _{the internal resetting of the} FIND key _{to function} as a SUPERFINO (i.é.v

it

will find only combinations

of records actually related to each _{other) after} a SUPERFINO has been donep _just as _the NEXT RECord and PREVious RECord keys do. _Similarly,

after a SUPERFINO, the AUTOFIND _{option is switched off} on all but _the main _fi1ep so _that those _fields may be _{edited without interference} from _undesired AUTOFIND'lng.

_If

_{the option of editing the} AUTOFINDing

fields is not desired9 editing can be _prevented by _{addition of the} NOFUT _{option to} such _fields.

The ENT$P£RMISSIVE _{indicator will allow operational} sequences like the one described above, which _{is normally} an _errom by _{not resetting the}

functioning of the FIND key and _the AUTOFIND _option. For those

situations in which

it

Is a permissible sequenceg the statement

DataFlex 2.0 User's Manual DATA ENTRY C-29

—

"INDICATE ENTSPERMISSIVE TRUE" _should be _{given prior to the beginning}

of the ENTER _or ENTERGROUP _{macro. This option} should _not be used _in

transaction-oriented applications in which _counters are provided and/or transaction totals are maintained.

C-30 DATA ENTRY _{DataFlex 2.0 User's} Manual ————————————————— ————————————————————————

THIS PAGE INTENTIONALLY LEFT BLANK

—

_ _ _ _ _ _ _ _ _ _ _ __~, ————————~——————~___————___========== C~31

_ _ _ _ = ~=~~~~——~~~~µ"~ —~~~————~

—

====

REPORTING AND OUTPUT ==========

""—~~

——————————

——

————

——

—————— ~==========~~———————~———————~—————~— —

Two areas _{of activity} consume a great portion of the development _time

for application software: (a) data _entry and

_file

maintenance; and (b)

_file

_{output for reports.} 1abe1sp _preprinted forms and

_files.

The DataFlex ENTER command macro provides a predefined

facility

for

dealing with the _{requirements in the}

_first

area efficiently; the

REPORT command macro takes care of the second.

The REPORT command macro consists of an integrated set of selectable predefined output routines that can be chosen as needed. You can use

In document DataFlex V2 Jul1984 pdf (Page 131-151)