DataFlex V2 Jul1984 pdf

(1)

D a

_t

a F I e X

Version 2.0

Appllcatfon Development _Software System

Copyright ,c) 1983. 1984 Data Access _Corporation DATA ACCESS CORPORATION

8525 SW 129 1"ermce Miamb _Florida 33156

USA

(2)

COPYRIGHT NOTICE

Corporation. All rights under _this _copyright are reserved worldwide. DataF1ex, _including _this manuañ which _is an integral part of

DataFlex, may not be reproduced, _transmjttedg _{stored in} any manner in

a retrieval system in _any form _{or through} any means, e1ectrica17

mechanica'L _opticab manual _{or otherwise without the} express written permission of Data Access _Corporatiom 8525 SW 129 Terraceg MiamL FL 33156, USA.

DISCLAIMER

Data Access _Corporation makes no representations or warrantiesn

express _{or implied,} With _{respect to DataFlex, this} manuab or any Data Access _Corporation productg _including _but not _limited _{to warranties} _of

merchantability or fitness for a particular purpose.

Data Access _{Corporation reserves} unto

_itself

_{the right} _to make

periodic changes, enhancements, _revisions and _alteration _of any kind to DataFlex _{and/or its} manual _{without obligation} _{to notify} any person,

institution or organization of such changes, enhancements, _revisions and _alterations _{to the product.}

TRADEMARKS

DataFlex and _Flex-keys are trademarks _of Data Access _Corporation. The trademarks and _registered trademarks _{of other} companies are

referred to at various points throughout this manual, annotated _with an asterfsk (*). The owners _{of the trademarks} are listed below:

MBASIC _Microsoft

CBASIC _Digital Research

CP/M _Digital Research

MP/M _Digital Research

WordStar _{MicroPro International}

MailMerge _{MicroPro International}

Pasca1/MT+ _Digital Research

dBASE

_II

_Ashton-Tate, _Inc.

PC-DOS _{International} Business Machines

IBM _{International} Business Machines

(3)

A COMPLETE, UPDATED MANUAL WILL BE YOURS . . .

If

we use a correction or Improvement _{to this} manual which you submit

to us.

We're _continually _improving our manual to make _the power of DataF1ex

easier to get to for the new _user. User feedback _{is the chief} _source

of corrections and improvements _{to the} manual. The _Disclaimer on the preceding page says that we aren't obligated to provide you with

updates _to DataF1ex

or its manual. but

if

we use a correction or improvement you send us, we'll send you a copy of the edition of the

manual which _{contains your update(sL} _{subject to the following:} (a)

If

we receive the same suggestion from _{several sources. only} the

_first

person submitting the correction/improvement gets a new manual; and

(b)

_If

we use two or more of your suggestions in one new edition of

our manual, you

_still

only get one manual _(multiple _suggestions

_still

increase your chances _of being

_first

on at least one of the

sugges-tions). Data Access _{Corporation's} _decision _{in these matters is}

_final.

A new manual does _{not include} a new binder (the old one is re-usable).

Herds How:

Just

_fill

out the form on the opposite side of this page indicating

what your suggestion is.

_If

you have _multiple _suggestions. _please make _{copies of the} form. Please make _your namep address, and phone

clear so that we can _get back to you

if

you win a new manuaK Send

the suggestion(s) to:

DOCUMENTATION

Data Access _Corporation 8525 SW 129 _Terrace Miami, _Florida 33156

(4)

SUGGESTION

For Improvement _of the Dataf1ex Version 2.0 _User's Manual

From: Submitted:

Name Date

Address Phone (A/C)

Address

City State/Prov. Zip

Country Page _Height: _in. x Width: inches

Revision Date _of Manual: Page Number(s):

TYPE OF SUGGESTION:

_

CorrectionAddition of missing informationof wrong information

C1aFification/Improvement of existing example

Addition of new example DETAILS:

I submit _the above _{suggestion to} Data Access _{Corporation with}

_full

permission to make any use of

_it

may wish tO9 _wIth the _{understanding}

that compensation _to me for ito

_if

any9 will be _{completely at the}

discretion of Data Acce9s _Corporation. _I _assume _no

liability

for its

completeness _{or accuracy.}

(5)

— ——

————— "=""""""'""""_{~ ...}

====

TABLE OF CONTENTS ———-— —

=,..'===

======———"="="—="====="""""""""""

~ ~

—

.

'u'" SECTION A: OPERATION AND ORIENTATION m'* ORGANIZATION OF THIS MANUAL

. . . A-l Sequence _{of Presentation.}

. . . A-l

Notational Conventions. . . A-2 OPERATIONAL ORIENTATION

. . . A-5

Installation. . . A-5 Runtime System.

. . . A-6

Application Development

. . . A-7 System Diagram.

. . . A-lO

Facilities of DataFlex Diagram.

. . . A-13 OPERATOR'S GUIDE.

. . . A-15

Definition of Terms

-

Operator. . . A-16 How _{to Begin.}

, . . . A-17

Flex-key Summary.

. . . A-18 Keyboard Command _Explanations

. . . A-19 INSTALLING DATAFLEX

. . . A-25 OPERATING TUTORIAL.

. . . A-33 QUERYING THE DATABASE

. . . A-41 Program _Start-ljp.

. . . A-41 Program _Operation

. . . A-43 Making _Selections

. . . A-44 Choosing an Output Sequence _. _. _. _. _. _. _. _. _. _. _. _. . . . A-44 Using QUERY _to Generate a Report Configuration. _. _. _. _. _. A-45

*** SECTION B: STARTING WITH DATAFLEX _'h'* PROGRAMMING TUTORÍAL.

. . . B-l FORMATTING WITH IMAGES.

. . . B-15 Image "Pages"

. . , . . . B-15 Images _in DataFlex _{Configuration} _Files.

. . . B-19 DESIGNING DATABASES

. . . B-21

Organization of Data.

. . . B-21 Data Types.

. . . B-22

Indexing in Applications. . . B-23 AUTODEF Program

. . . B-25 HOW TO WRITE A CONFIGURATION.

. . . B-29

Creating the Source _File.

. . . B-29 How _to Compile a Configuration. _. _. _. _. _. _. _. _. _. _. _. _. _. B-31 How _to Run _a _{Configuration.}

. . . B-33 DATAFLEX UTILITIES.

. . . B-35

Editor. . . , . . B-35 Reindex

. . . B-39 Free _List (FREL).

. . . B-43 Read.

. . . B-44 How _to Convert dBASE

_II

_Files _to DataFlex

. . . B-44 DataFlex 1.6X _to 2.0 Conversion

. . . B-51 Menu _Creation and Maintenance (MENUDEF)

. . . B-53

—

(6)

ii

TABLE OF CONTENTS DataF1ex 2.0 _User's Manual

*H SECTION C: PRE-PROGRAMMED FACILITIES _*** ELEMENTS OF CONFIGURATIONS.

. . . C-l

String Constants. . . C-2

String Variables. . . O . . . C-2 Numeric Constants

. . . . Q . . . C"3 Numeric _Variables

. . . . q . . . $ 0 . . . C-3

Expressions . . . P . . . Q . . e . . « . . C~4 Date _Variables.

. . . O . e ¢ O . . . C~5 Date _Constants.

. . . O . O O Q . . . C-6 Filenames

. . . P . Q . . . C~6

Indicators. . 0 . 0 . , * O O . O 0 . . . C—7 DECLARING DATA ELEMENTS

. . . C-9 STRING Command.

. . . 0 J . . Q . . . e . . . . C-9 NUMBER Command.

. . . C-lO DATE Command,

. . . , , O . . O . Q e . . . C-lO INTEGER Command

. . . Q . . . , C-ll INDICATOR Command

. . . C-12 MANIPULATING DATA ELEMENTS.

. . . C-13 MOVE Command.

. . . 3 . . . C-13 INCREMENT Comnand

. . , O . . O g . . . C-14 CALCULATE Command

. . , . . . C-14 DATA ENTRY.

. . . 0 . . . C-15 ENTER Command Macro

. . . a . . . C-15

Structure of an ENTER _{Configuration}

O . . . C-17 Images _in ENTER

. . . e , , U . . . C-18 ENTRY Command

. . . Q . 3 D . P . H . . . C-19 ENTRY Format _Options.

. . . ,, . . O . . . 0 C-19 ENTRY and AUTOPAGE.

. . P 9 e . g U . . . C-21

User-Oefined Procedures _of ENTER.

. . . C-24 ENTDISPLAY Command.

. . . O . . . C-26 ENTER Sequence _{of Operation}

. . . . U . . . C-27 ENT$PERMISSIVE _Indicator.

. . . C-28 REPORTING AND OUTPUT.

. . . Q . 0 . . . C-31 The REPORT Command Macro.

. . . . O O . . . C-31

Sections of REPORT.

. . . 0 . . . C-31

Subtota11ing and _Tota11ing.

. . . Q O . . . C-34

Selective Reporting . . . O 0 e 3 . . . O . . . C"38 Page _Control.

. , . . . . Q , , O O @ . . . C"41 Things _to Remember About the REPORT Macro

. . . C-45

,~

(7)

DataF1ex 2.0 _User's Manual TABLE OF CONTENTS

iii

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

SECTION C _(continued) FILE DEFINITION (FILEDEF)

. . . C-47 Step One

- Plan the Relationships Among the Files . . . . C-48 How _to Create _{Related Fields.}

. . . C-50 Step Two

- List the Fields. . . C-53

Overlapping Fields. . . C-54 Step Three

- Determine the Key Fields . . . C-55 Step Four

- Use FILEDEF to Put

It

Ali Together. . . C-56

Creating/Edlting Fields . . . C-60

Creating/Edlting Indexes. . . C-63

Print File Definition . . . C-65 Set _Fi7e Parameters/Names

. . . C-66 Erase Data _File

. . . C-66 Set _File _Inactive

. . . C-66 Create _{File Definition} from Screen Image.

. . . C-66 Create _{File Definition} from .DEF _File

. . . : . C-67 Save _{Definition/Exit} FILEDEF.

. . . C-67

Abort FILEDEF

. . . C-67 SAMPLE APPLICATIONS

. . . C-69 P

*** SECTION D: PROGRAMMING DATAFLEX 'H'* DIRECT CONTROL OF DATA ENTRY.

. . . D-l PAGE Command.

. . . D-l ACCEPT Command.

. . . D-l DISPLAY Command

. . . D-2 AUTOPAGE Command.

. . . D-3 CLEARFORM and BLANKFORM Commands.

. . . D-3 OUTFILE Command

. . . D-4 OUTCLOSE Command.

. . . D-4 OUTPUT Command.

. . . D-5 NAME Command.

. . . D-5 FORMAT Command.

. . . D-6 PRINT Command

. . . D-7 ENTERGROUP.

. . . D-8 MANIPULATING STRINGS.

. . . D-ll LEFT Command.

. . . D-ll RIGHT Command

. . . D-12 MID Command

. . . D-13 ASCII Command

. . . D-13 CHARACTER Command

. . .

.'.

. . . D-14 POS Command

. . . D-14 LENGTH Command.

. . . D-15 PAD Command

. . . D-15 TRIM Comnand.

. . . D-16 APPEND Command.

. . . D-16 UPPERCASE Command

. . . D-17 CMDLINE Command

. . . D-17

String Operations . . . D-18 CONDITIONAL EXEQ/TION

. . . D-19

Setting Indicator Status. . . D-20

Predefined Indicators . . . D-24 IF _Test

. . . D-24

—-————-————

(8)

iv TABLE OF CONTENTS DataFlex 2.0 _User's Manual

SECTION D _(continued) CONTROLLING EXECUTION SEQUENCE.

. . . D-29 GOTO Command.

. . . 0 . . . D-29 ON GOTO Comand

. . . O O . . Q P . . . D-30 GOSUB Command

. . . D . . . e D-30 ON GOSUB Command.

. . . U . . . D-31 RETURN Command.

. . . D-31 CHAIN Command

. . . D-32 CMDLIME Command

. . . D-32 DEBUG Command

. . . P . . g . . . D-33 ERROR Command

. . . G . . . Q . . . Q . . . D-33 CLEARWARNING Command.

. . 0 . . . D-34 ABORT Command

. . . D-34 BLOCKS AND LOOPS.

. . . 0 . . . D-35 BEGIN

- END Command . . . D-35 REPEAT

- UNTIL Command. . . Q Q . . . D-35 REPEAT

- LOOP Command . . Q . . . D-36 WHILE _~ END Command

0 . . V P . . P . . S. D . O . . . D-37 FOR

- FROM - TO - LOOP Command. . . D-37 DIRECT CONTROL OF THE CONSOLE

. . . D-39 SHOW Command.

. . . D-39 SHOWLN Command.

. . . D . . . D-40 INPUT Command

. . . O Q e . . . D-40 GOTOXY Command.

. . . 9 . . . D-41 CLEARXY Command

. . . 0 . . . D-41 CLEARSCREEN CQmmand

. . U . 0 D 8 0 . G . D . . 0 . e & . 0~42 KEYCHECK Cownand.

. . . D-42 INKEY Command

. . . Q . . e U . . . D-43 SCREENMODE Conmand.

. . . . 3 . . D . . . D-43 MANIPULATING RECORDS.

. . . O . . . D-45 Database Commands and FILEDEF

. . . , D-45 Record _Buffers.

. . . . * . . e P , 0 3 . . . , . . . D-45

File Definition . . . D-46 OPEN Command.

. . . O . q . . 0 . . . D-47 FIND Command.

. . . , . 0 . . . 0 . . . D-48 SAVE Corrmand.

. . . D-51 SAVERECORD Comand.

. . . e . . . D-51 CLEAR Command

. . . P 0 . . . D-52 DELETE Comiand.

. . . D-52 RELATE Command.

. . . D-52 ATTAM Command.

. . . D-53 ZEROFILE Command.

. . . Y . . . U . . . D-54 System _Files.

. . . a Q . 0 . . . 0~54 MANIPULATING FILES.

. . . Q O . . . D-55 ERASEFILE Command

. . . D-55 RENAME Command.

. . . D-55 COPYFILE Cormand.

. . . O . . . D-56 DIRECTORY Command

. . . D-56 FILELIST Cormand.

. . . e . . . D-56 SYSTEM Command.

. . . 0 G D . . . D . . 0~57 RUNPROGRAM Command.

. . . D-58 REGISTRATION Command.

. . . D-58 SYSDATE Command

. . . D-58

——————-—————————-—

(9)

DataFlex _{2.0 User's} Manual TABLE OF CONTENTS v —————————————————————————————————————

SECTION U _(continued) DIRECT INPUT AND OUTPUT

. . . D-61 DIRECT_INPUT Command.

. . . D-61 DIRECT_0UTPUT Command

. . . D-62 CL0SE_INPUT & CL0SE_OUTPUT Commands

. . . D-62 READ Command.

. . . D-62 READLN Command.

. . . D-64 SEQEOF and SEQEOL _{Predefined Indicators}

. . . D-65 WRITE Command

. . . D-66 WRITELN Command

. . . D-67

Reporting Without Report. . . D-67

*** SECTION E: ADVANCED CONFIGURATION *'H' USING FUNCTION KEYS

. . . E-l Using _{the Flex-key Indicators}

. . . E-2 Using Key Procedures.

, . . . E-2 ENTAGAIN

_Cand.

. . . E-4 ENTERMODE Command

. . . E-4 BACKFIELD Command

. . . E-4 HELP Command.

. . . E-5 MULTI-USER FUNCTIONS.

. . . E-7

Multi-User Operation Under _the ENTER Macro.

. . . E-8 LOCK Command.

. . . E-9 UNLOCK Command.

. . . E-9 REREAD Command.

. , . , . . . E-9 IFMANGE Command.

. . . E-9 SETOANGE Command

. . . E-lO DESPOOL Command

. . . E-lO FIELDINDEX AND WINDOWINDEX.

. . . E-ll MODIFYING AND EXTENDING DATAFLEX.

. . . E-13 Replacement

. . . , . . . E-14 Command _Definition.

. . . E-14

Include Files . . . E-16 Compile Time _Variables.

. . . E-16

Conditionals. . . E~l7 CHECK Macro Cmmand

. . . E-18 Symbol-Checking _Characters.

. . . E-19

Internal Typing _of Symbols.

. . . E-20

*** SECTION F: APPENDIX _*** RESERVED WORDS OF DATAFLEX.

. . . F-l FILES, ARGUMENTS AND COMMANDS

. . . F-3

Predefined Arguments.

. . . F-4 Window Format and _Entry Options

. . . F-5 Command Syntax _List

. . . F-6 SPECIFICATIONS.

. . . F-9 COMPILER ERROR NESSAGES

. . . F-13 RUNTIME ERRORS AND DIAGNOSIS.

. . . F-19 GLOSSARY.

. . . F-35 TP'3LE OF ASCII CODES.

. . . F-41 '-lfjEX

. . . F-43 ==========""

(10)

vi TABLE OF CONTENTS DataF1ex 2.0 _User's Manual

list

of sample screens Sample Screen _{A-l -} Master Menu.

. . . A-34 Sample Screen A-2

- Configuration menu _. _. _. _. _. _. _. _. _. _. A-35 Sample Screen A-3

- Vendor Master Record . . . A-36 Sample Screen A-4

- Demo Inventory System Menu . . . A-42 Sample Screen A-5

- File List-Demo Inventory System. . . . A-42 Sample Screen B-6

-

Personnel Record, Prompting in AUTODEF B-5

Sample Screen B-7

- Configuration Mentn Select to Run

Configuration. . . B-9 Sample Screen B-8

- "PERSON'4 Showing Sample Data. , . . . B-17 Sample Screen B-9

- Menu Edit Selection. . . B-53 Sample Screen _{B-lO -} Menu _{Configuration.}

. . . B-54 Sample Screen _B-ll

- Menu System Question Entry and Editing B-56

Sample Screen C-12

- File Definition Menu. . . C-59 Sample Screen C-13

- File Definition Field Edit Option Menu C-60

Sample Screen C-14

- Inventory Customer Master File. . . . C-70 Sample Screen C-15

- Inventory Item Master File. . . C-81 Sample Screen C-16

- Inventory Invoice Entry . . . C-86 Sample Screen D-17

- Report Configuration Not Using REPORT

Macro

0 . C . . . O e 0 0"68

list

of sample _{configurations}

Sample _{Configuration} _{B-l -} Personnel Record,

_Initial

_Entry

. . B-2 Sample _{Configuration} B-2

- Personnel File, After AUTODEF . . . B-7 Sample _{Configuration} B-3

- Personnel File, After Customization B-13

Sample _{Configuration} B-4

- "PERSON" Entry Screen . . . . , , . B-15 Sample _{Configuration} B-5

- "PERSON" Plus "JOB" . . . O . . . . B-17 Sample _{Configuration} B-6

-

Systtm Date Dfsp1ay/Entry O . Q . . B-30 Sample _{Configuration} C-7

- Simple ENTER Configuration. . . O . C-23 Sample _{Configuration} C-8

- ENTER Configuration Using User-Oefined Procedures

. . . 0 . . C-25 Sample _{Configuration} C-9

-

_entdisplay.ENTER Configuration Using

. . . Q . c-26 Sample _{Configuration} C-id

-

Simple Report Using REPORT Macro . C-33 Sample _{Configuration} _C-ll

- Complex Report Using REPORT Macro. C-37

Sample _{Conflguration} C-12

- REPORT_and _PageWith Operator Selections

Control . . . C-42 Sample _{Configuration} C-13

- Screen Image for FILEDEF to

Work From.

. . . C-53 Sample _{Configuration} C-14

- Inventory Customer Master File . . C-74 Sample _{Configuration} C-15

- Inventory Customer Report. . . C-77 Sample _{Configuration} C-16

- Inventory Vendor Master File . . . C-80 Samp7e _{Configuration} C-17

- Inventory Master File Data Entry . C-84 Sample _{Configuration} D-18

- Personnel File, Using ENTERGROUP . D-9 Sample _{Configuration} D-19

- Illustration of FIND Command . . . D-50 Sample _{Configuration} E-20

- Update Routine in Multi-User

Environment. . . E-IX) Sample _{Configuration} E-21

- Use of WINDOWINDEX Predefined

Variable . . . E-12

__—"—

——

(11)

_——

————

—"~——" ===""=="""

=:

:::::

ORGANIZATION OF THIS MANUAL

====

—————===== ==========

__"

_

"",

SEQUENCE OF PRESENTATION

The sequence in which material is presented in this manual is the recommended sequence for the undertaking of tasks in learning DataFlex

and _{in using}

it.

Your _learning _{experience with DataFlex will} rapidly

become _a _productive experiencep _{in that within} a _{couple of} hours, you

will be _{able to create} database _structures and _control them _with

configurations. Configurations is the word used _{in this} manual _for a data _{processing procedure,} or _{program written} in DataFlex. Your

early exercises will yield simp1eg _{straightforward} _applications _which

despite their simplicity will have more than enough power to efficiently perform any number _of cormon data _{processing tasks,} such as mailing

_lists.

But you _{very likely} acquired DataFlex because

_its

power and

flexibility

go far beyond mere

_list

management. As you continue reading this manuá1» and _testing _the

_facilities

_{described in} each

section, possibi7ities for greater scope and _{sophistication}

_will

multiply rapidly until you reach _{the point at} which you have _the means

of satisfying all of your data management needs. The _simpler

fac1l1ties of DataF1ex _are so powerful that you may reach this point

well" before you explore the more advanced _features _{of Datañex}

described in later sections.

_If

this happens, _{there is} no need _to study _further _{except to generally} _{acquaint yourself} _{with the}

capabilities of the more advanced _features.

————————

(12)

A-2 ORGANIZATION OF THIS MANUAL DataF7ex 2.0 _User's Manual

NOTATIONAL CONVENTIONS IN THIS MANUAL

Certain notational conventions are used _{throughout this} manual _with which you should become _{acquainted in order to} understand _{the formats} and examples shown. _{DataFlex configurations} are made up of screen images (always _{at the beginning)} and then comand _lines, _the two

sections being separated by _{the distinctive}

_"l*"

_{character combination} by

_itself

on one line. DataF1ex commands are like sentences made up

of a verb _(the cormand) and _(usually) one or more objects (referred to

as argumentsL sometimes _followed by one _or more options, and

sometimes _further _followed by _a comment. Commands may be preceded by

conditional terms _called _indicators. _Lastly. some command _lines begin

with "labels". distinguished by a terminating colon (LABEL: _L, whose purpose

_it

is to "mark" a spot in a configuration for purposes _of

future references (such as a RETURN _or GOTO connand). Here _{is the}

typical format _of a command line:

[indicator] command argument _{options} //comment

The _{brackets [] surrounding the indicator} are required to identify

indicators. The braces _{{} surrounding the options} are not to be typed

in most commands, except _{fbr format options for} the ENTRY and FORMAT commands, where _{they are required.} The braces are used _{in format}

i11ustrationm howeverj _{to signify} an optional command _element. Again. _they are not to be typeci _{in the} comand except _{in the} cases

noted. The

_"//"

_{twin diagonals} which precede _the comment _{are, like}

the indicator bracketsp _{part of DataFlexG} syntax,p and

_tell

_DataFlex

not to compile the _material _following _{the dlagonalm} which _leaves them

free for any materia] you may wish _{to include in the} source version of your configuration for reading by persons (as _{distinguished} from the

computer). Twin _{diagonals at the beginning of} _a _line

_will

cause the

entire line to be a comment. Here _is a typical command _line: [FOUNDI ENTRY mai1.name {CAPSLOCÍO

_{// first}

_try

This line starts with a (DataF1ex-supp1ied) indicator» FOUND, which _is enclosed _{in the required brackets,} _followed by _{the comand,} ENTRY. then the argument, which _is a screen image window named _{(in the}

ccmfiguration) MAIL.NAME, _followed by _a _formatting _option _(this one does _{require the braces).} CAPSLOCK.

_It

meansp

_"If

the desired record is successfully FOUND _{in the} databaseg _{put the cursor into the} next screen image window and accept _for ENTRY _{into the} database element MAIL.NAME _{the characters} keyed _into the windoWg _but _as though _the CAPSLOCK key were on (lower case characters converted to uppercase)."

The _coment

_(first

_try) _{is not interpreted} by _DataFlex and hence has no meaning _{for execution;}

it

would have meaning _{only for} a person

reading the configuration.

The example above _illustrates _the use of upper and _lower case in

(13)

DataFlex 2.0 _User's Manual ORGANIZATION OF THIS MANUAL A-3 ——

—

examples _{throughout this} manual. FOUND, ENTRY, and CAPSLOCK are all in capital 1etters9 while mail.name _{is in lower} case. This is intended to signify that FOUND, ENTRY, and CAPSLOCK

are iñteral strings which match» _{respectíve1y9} _an _indicator. a command and an

option which are inherently part of DataFlex. In any configuration which _you _{wrote using} these e1«nents, you would have _{to 1itera11y} use these _strings _{then. also.} _Mail.name, on the other hand. _{is peculiar}

to the example _{or configuration} which _is being discus5edp and would

typically be some other string in any configuration written by you

(although you could use

_{it if}

you chose _to). You

_will

_{find this} use

of upper and _lower case throughout the formats and examples _{in this} manuab except _for the

_full

sample _{configuratioñs»} which _{follow the} normal _{configuration} _{convention of} being _written _{in solid} _capital

letters except _{for textual} _material in screen prompts and messages which need upper and _{lower case.}

Throughout DataF1ex, _in the _systw _as _well _as _{in this} manual, _material enclosed _{in either} _single

_(')

_or double _(") _quotation marks _is

_literal

material which passes through configurations as such and _{is displayed}

or outPutg _rather than _executed.

DataFlex

_itself

has many syntactical conventions in addition to the

ones described above, which are peculiar to presentations in this

manual. _DataFlex's own syntactical conventions are described separately at the appropriate places in this manual.

(14)

A-4 ORGANIZATION OF THIS MANUAL _DataFlex 2.0 _User's Manual

THIS PAGE INTENTIONALLY LEFT BLANK

(15)

_ _ _ _ _ _ _ _ _ ————————————————————————__=========A—5 ~~~

————

——————

"""==="""" OPERATIONAL ORIENTATION "

"""""

————— This section describes the steps involved in developing an application

in DataFlex and _{the various}

_files

and programs that come into play

both _{in creating} and _{in running}

_it.

DataFlex _offers a wide range of

_facilities

for applications

development. Because _{of this,} _{there is frequently} more than one way

to achieve a particular goal. Since one _{or another of the alternative} methods _{is normally preferable} under _certain _{circumstancem care}

should be taken _{to avoid thinking} _{that the}

_first

way conceived _or implemented _for doing a task is the only, or bésto way. Any method developed _{for doing} a task should be reviewed _{against the possibility}

that an alternative approach _might be _easier or more efficient.

Thjs section is divided into two _parts: Runtime Systm and

Applica-tion Development. The _runtime system _{is the part of} DataF1ex _required

to execute _{(run) the application.} The _person(s) who run the applica-tion is(are) referred to as the "operator" (as distinguished from the

configuratom who _{is the} person who develops _{the application).} The

application development _{section describes the parts of} DataF1ex which

support development _{of applications.} Although _{the configurator} and the _operator may in some instances be the same persom the _activities

of configuring on the one hand and operating on the other are

differ-ent, so that

_it

is useful to distinguish between these _functions.

INSTALLATION

The _installation _of DataFlex _{consists mainly of} copying _the necessary

files from your DataFlex master _{disks onto your} working _disks or hard

disk drive and then using _the DataFlex SETSCREEn program to

_initialize

the system _{for your serial} number and _terminal _type. The SETSCREEn program reads the

_file

TERMLIST.CFG and _{writes the terminal}

informa-tion input by _the user _{to the}

_file

FILELIST.CFG _to be used by _the

runtime system and _{the configuration} _systm. See the _installation

instructions and _{the section} on Installing DataFlex for more

informa-tion on insta11ation.

===ma==: _——————————————~—~~~—————~_~_____"____""_

(16)

A-6 OPERATIONAL ORIENTATION DataFlex 2.0 _User's Manual

"==========~

_"""""

RUNTIkE SYSTEM

The _{basic operating} nucleus _{of the} DataF1ex _runtime system _{is the} program "FLEX.COM" (FLEX.CMD on CP/M-86 _systems). FLEX.COM and

_its

overlay

_file

"RUN.OVF" are functional all the time any DataFlex

configuration is running. The _{DataFlex configuration} _{contains the}

intelligence which enables DataF1ex _to make _the computer do a

particular task. just as a BASIC program works _{through the} BASIC

interpreter. Without a compiled configuration (.Fl-X)

file,

the

runtime system can do _nothing.

Under _control _of a configuratiom the DataFlex runtime system can access and _manipulate one or more databases9 _interact _{with the}

operator, drive the printer, read and _write _standard ASCII

_files.

and

otherwise activate just about every function found _in microcomputer systems. These _activities _{are controlled} by _{configurations}

_(files

with the _{".FLX" extension)} _created and compiled by _{the developer.} When FLEX _is run from the _operating _system _the name of the configuration which _{is to} be _run must be given _with

_it.

When _initialized, the _{DataFiex runtime} system

_first

reads a

file

called FILELIST.CFG which _contains _information about what database

files

are available, and _information which enables _{DataFlex to}

generate the _control codes which _will _{operate your particular}

terminal.

Each data base

_file

name _{appearing in} FILELIST.CFG _actually _refers _to a "family" of related

_files

on _{your disk.} all having a cormon

root-namep but _different _extensions. The _data

files

(".DAT" extension) contain the raw data _{in the} sequence in which

it

was entered, and _the

basic information on the structure of the data

_file.

The key

_files

(".Kx" extension where _x _{is the} number _{of the index) contain index} data which _provides _access _to the data by indexes _established by _the

configurator during the process of defining the database. The tag

file

(".TAG" _{extension) contains the} names _{of the fields} which make up

the database.

Thus the minimum

_file

comp1©ent _{required to} _run DataF1ex _consists _of: FLEX.COÑL RUN.OVK FILELIST.CFG, _{at least} one .Fl-X _{(configuration)}

file

previously created by _{the configurator,} and _all database

_files

(.DAT) .Kx and .TAG) _for _any _{database(s) declared in} (used by) _the

configuration(s). To use the QUERY

_facility

_the QUERY.COM and QUERY.OVF program

_files

must _also be _present.

(17)

DataF1ex 2.0 _User's Manual OPERATIONAL ORIENTATION A-7 ———————

+ ~

_===""4"""

h

The _DataFlex Menu System _{that greets the} user when DataFlex _is

initialized is

_Itself

a _{DataFlex configuration.} The name _{of the} menu

configuration is MENU.FLX. The menu

_facility

keeps _the menus in a

standard DataF1ex data base

_file

whose name _is MENU.DAT. MENU.DAT _is

installed as

_file

49 _{in the}

_list

_{of active} databases _in FILELIST.CFG as supplied. Thus _to use the menu

_facility

you must have MENU.FLX and MENU.DAT on _your system.

Other _supplied programs may be _{required occasionally} _at run _time. REINDEX reads a data

_file

and _rebuilds _the keys _{(.Kx files)} _in case

they are damaged by a power, medía _or system _failure. Reindex _is

also used _{to maintain} BATCH indexes and _create "ad hoc" _indexes. The FREÍ- _((Fre)e _(L)iSt) program reads through a data

_file

and _verifies

(and _rebuilds

_if

necessary) _the

_list

_{of deleted records in} a _data base

file,

and _{also deletes or extracts} any records that appear damaged

(typically as a consequence of a power, media or system _failure). Both _of these programs may be _{kept off-line} _until needed.

APPLICATION DEVELOPMENT

The process of developing specific applications in DataFlex _involves

creating configurations

_(files

with the .FLX _extension) and database

files

to store and _manipulate data _{in the desired fashion.} These

files

are created by use of a group of

utility

programs supplied with

DataFlex. The .Fl-X

_files

are created by _{running the} DataFlex COMPILER program on "source"

_files.

Source

_files

can be _created by any of several different means, including the EDITOR.COM program supplied with DataF1ex9 _or any text editor or word processor which _{is capable}

to producing plain ASCII _text

_files

_you _might happen _{to favor.} The source

_files

contain all the various comands _in DataFlex which _cause

the systw to carry out the desired processes.

You _will _probably produce _your

_first

_{configuration} using _the AUTODEF

utility.

AUTODEF _{also creates the definition} _for a new databaseg and

the data and key _files necessary for its data. To use

_it.

the

_first

step is to "draw" an image _{of the input} and query screen that you

_will

use on your new database (see the section Qñ "Formatting With

Images"). The DataFlex EDITOR _or _your _favorite _text _editor _will _serve

for this purpose. AUTODEF reads _this

_file

and produces both a

file

definition (.FO)

_file

and a configuration SOURCE code

_file

_(with a .FRM _extension), ready _to be _compiled. The _{configuration} produced by AUTODEF can perform

_{full file}

maintenance on the database

_file

it

creates.

(18)

=""="===~—

—— _{————+———————————""""}

""

The _function _{of the} EDITOR program is to create, display and mod'ky

DataFlex configuration SOURCE and IMAGE

_files.

The source

_files

can be _created from _{scratch with} the EDITOR, or can come from one of the auto-definition

_utilities

like AUTODEF, QUERY _or READ. The source

files

produced _with EDITOR are standard ASCII

_files,

so most word

processors or editors can be used _{instead of the DataFlex} EDITOR

_if

you are more comfortable with one of them.

The DataFlex QUERY program _{provides the} user easy access _{to the}

information stored in any database _existing on the disk drive. The QUERY

_facility

_can be used _as _an ad hoc _{report generator that} _requires

little

trafning to use. QUERY _{is entirely} _{prompt-drivem} making

it

quite practical for use by _{operators9 but} once a query has been

successfully perforTned»

it

permits storing the query criteria in a

file

as source code _for a report configuration. The _source

_file

can then be compiled _to become a permanent _report. QLJERY _requires _all _of

the standard _runtime database

_files

_to be _present.

The _DataFlex READ _{conffguration} _generates a source program to import standard ASCII data

_files.

READ _{is primarily} _{intended for} those who are converting to DataFlex from _other systems.

The CVTFRM and CVTRPT programs read _{DataFlex configurations} _written under _earlier _{versions of} DataFlex _(1.6x) and produce _DataFlex 2.00 ' source configurations. Configurations written in Versions l.6x of

DataFjex are fully convertible to configurations which run under

Version 2.OX by _use _of these

_utilities.

Natura11y7 _{configurations} produced _{in this} _{fashion will} _{not take} advantage _{of features of}

Version 2.Ox which were _{not present in the version of DataFlex} under which the _original _{configuration} was producecb but _{the converted} source

file

can be _{edited to} do so

if

desired.

The _compiler (COMP.COM _or COMP.CMD, _and--for _B-bit systems--COMP.OVF) which produces .FLX

_files

from source

_files

requires three

_files

to be

present on the logged-in disk drive in order to do _{its job:} _the

configuration source fi1eg a

_file

_definition (.FO _extension)

_file

_for each database _declared by (used _{in) the configuration,} and FLEX.CFG

the DataFlex command macro

_file.

The .FO

_files

and FLEX.CFL must both

reside on the logged-in (defau)t) disk drive. A _successful

compilation will produce a runnable DataFlex configuration with the .FLX _extension and _the same rootname as the source

file.

As the

compiler runs,

_it

will display on the screen the original source commands _{together with line} numbers assigned _to them by _{the compiler} and any _error messages which _{arise during} compi7e _time. _{This output} can be _directed _to any of three devicmm _{the consolm the printem} or a printab7e (.PRN)

_file.

(19)

DataFlex _{2.0 User's} Manual OPERATIONAL ORIENTATION A-9

A DataFlex _{configuration} _that does _not use any database(s) would _not

require any .FO

files

in order to be compl1éd» but the typical

Data-Flex configuration wIll access one _or more databases. The .FO

files

are used _{only at compile}

_tim;

_they are _{not required at} run time. On

the other hand, _{the other runtime} database

_files

(.DAT, .Kxp .TAG) are not _required by _compile. _{This difference} _in

_file

_requirements can be taken advantage _of when _{operating within} _restricted _disk space.

The FILEDEF

_utility,

_like AUTODEF, _Is used _{for creating} database

_files

and _{configuration} source

files.

FILEDEF _is more versatile than

AUTODEF.

_Multi-file

_{relationships} can be _{created with} FILEDEF. FILEDEF _requires more extensive knowledge _{of DataFlex, but gives} more

control over the database. The FILEDEF program can also read and

write database _definition (.DEF) _files _{in standard} ASCII. _Definition

files

are useful for reference, database documentation and transfer' of

applications to other environments.

The PACK program is for use by users who want _{to create their} own new commands and add them _{to the DataFlex} language. The PACK _program reads _the

_file

FMAC and _{creates the}

_file

FLEX.CFL which _is used by _the

compiler. New command macros are added _to FMAC _with a text editor or word _processor and then made usable by _running PACK on the new version of FMAC, _creating _a new version of FLEX.CFL _(overwriting _{the old one).}

P

(20)

Y

\

¢aMFhgURATjaA/ S runt/he

i

_Á

um

! I l

J ),

t

I

"FLEX"

\

'

_\

I _runtihe

query

)

read

I

_editor

I

C

b

i

FjLEDEF)AU}aDEF

I

i

[i

'

l

_a

A A

a

t

a wage

p I

PRINTER' b

source

""

)

'Ej

'tj:

ccwpiler I pa0gaaá( _file

-:

'

)

'Li

q:

i'

DATAFLEX

systehdiagrah _I

1//

\

set

(21)

Dataflex 2.0 _User's Manual OPERATIONAL ORIENTATION _A-ll ————

—————————————————————————————————— .

After running SETSCREEn and _"informing" _{DataFlex of the} codes which

operate your terminab there are three basic levels of using DataFlex through which you should proceed _{in order for} the _easiest» most thorough _learning _experience. The _{content of this} manual _is

_itself

presented _{in the order} which _will _best

_facilitate

_this approach. They are described below:

QUERYING AND REPORTING Your _DataFlex system was supplied with more than a dozen _{working configurations} complete _with sample datap

_all

on diskp compiled and ready _{to run.} They _{are intended} as learning aids

and _are _not documented _{in this} manual. You

_will

_find most _of them

listed in the "DataFlex demo

_files"

submenu, which you may choose from

the master menu. From _this submenu, you may actually run any of the configurations, and/or query their databases, by _electing _{the last}

choice, "QUERY Data _Files." You should _tour these samples _free1yg

entering additional test data where you choosep and _{running reports} _to

the screen _{and/or your printer} from them _at

_will.

The _Operator's Guide _{in this} manual should _{provide all} _the guidance you will need in

this activity. Eventua]lyp you may even wish _{to modify the}

configurations themselves _to make them run differently. (Sane _{of the}

configurations may happen to be already very close to something you

could actually use for your own purposes.) The source "code" (which

is what must be _modified and _{recompiled to} change _{the configuration)}

is supplied for every configuration on the C: _disk.

PROMPTED DATABASE CREATION AND CONFIGURATION DataFlex _provides numerous "automated" methods _{for creating} and _maintaining databases and _{for creating} _{the configurations} you will need _{for entering data} to» and _reporting data from those databases. While _{the "shortcut"} methods are promptecb and _typically more narrowly structured than the

"programming" methods _{of writing} _{DataFlex configurations,} they _should

not be _{underestimated.} In _actua1ity7 _{they are highly flexible} and

very powerful in their own right. Roughly two _{out of four DataFlex} users

_will

have no regular occasion _to use any DataFlex

facility

other than EDITOR _(for _writing _{configurations),} MENUDEF _{(for creating} and

editing menus). AUTODEF _{(for creating} databases and _entry

configura-tions) and QUERY _{(for creating} _reports and doing _interactive

inquiries). Of _the remaining two _{out of four typical} DataFlex _users,

only one will have _requirements which cannot be _fu1fi17ed by the

aforementioned

_facilities

plus the ENTER _macro and _the REPORT macro. The

_facilities

mentioned above should be _{explored thoroughly.} You should proceed on to the next stage _{only in the event that} you have unusual _requirementm or a driving curiosity as to the virtually limitless possibí7itíes offered by _the most _{extensiveg flexible}

applications development medium _available 'in _today's market.

——————

————-—— ———

(22)

==""""==="""=—"""""""""""""""""""""" " = "' =====

—===""_".==_""====""""""""""""

_""""

""""""""""""""""

PROGRANING AND EXTENSION OF THE LANGUAGE In _line-by-line programming

of app1icatiorm DataFlex offers

_facilities

for the creation of applications not even _yet imagined by _its _creators. The more fundamental _functions _{provided in function} key commandsg _sequential

input/output9 console inputloutput and _multi-user _functions _{allow the}

construction of virtually any processing structure which _could be

desired. Although whole _{configurations} can be made up of such commandm these commands are more likely to be used _intermingled _with

structures created by _the pre-programmed

_facilities

such as the REPORT and ENTER macros. While exclusive use of these

_facilities

_{for writing}

configurations is likely to be _a _{less efficient} way of creating configuratiorm occasional use _of them _{to alter} _the way standard

structures function Is very much encouraged. _{In the} Advanced _section

of this manuab you

will

even find procedures _{for modifying} DataF7ex commands themselves, as well as procedures _{for creating} _entirely new commands _{for your individual} use.

The schematic on the next page offers a graphic depiction of the

ranges of programming _{sophistlcatíon} _to which each _{of the}

_facilities

of DataF1ex _primarily _applies. The _chart should _not be _interpreted

too

_literally.

There _is no reason whatsoever Whyg _for examp1ep _the

"basic"

_facility

of QUERY should _not be used _in an otherwise

"advanced" _application _{to create} one _or more reports

_if

QUERY _can

satisfy the applicatioMs requirvments for that particular function. Furthem a common way _{of creating} highly complex _applications _involves

the use of "basic" or "intermediate"

facilities

such as QUERY _or AUTODEF _{to create the "nucleus" of the app1icatiom} and _then subsequent _editing _{of the} nucleus _{to incorporate} _the more "advanced"

features required by _{the application.}

P

——

_{_}

,,,—,

———————————

="" "" . ——,.,, .

_{_~_,}

_===__~—___~

(23)

DataFlex 2.0 _User's Manual OPERATIONAL ORIENTATION A-13

---THE FACILITIES OF DATAFLEX

—---LEVELS OF CONFIGURATION

SOPHISTICATION---OPERATOR BASIC INTERMEDIATE ADVANCED

llllExISTINGllllll

llCCNFIGURATIONSll

llllllWERYlll|lllllllllll:

_{ll::lllllllll:|llllllllllllll:llllll;ll}

_llllll

;llllMENUlllll|lllll:

_{lllllllllllllllll|:ll:llllll;lllllllllll:lll:}

_llllll

lll|AUT0DEFllllllll;:

_{lllll;lll|lll|l:llllllll|llll:lllllllllllllll}

_llllll

llllEDITORlllllllll|:

_{lll:llllll:ll:l:lllll:l::ll}

_llllll

lllSCREEN

_{IMAGES|llllllllllllllllllll:}

ll|llllll:

llllll

:

lllC0MpILERllll;;l}|lllllll:l:lllllllll:lllllll llllll

llllANUDEFl:

_{ll}llll|l::lllllll:llllllllllllllll|lllll}

ICONTROL C0MMANDSlll:

|lllllll:lllllllll}llllllllllllll

lmost

_{comandsllllllllllllllll}

llllll

ll: lINDICAT0RS:lllllllllll:lll

_llllll

lllREPoRT

_{MACROlllllllllllllll}

llllll

llllENTER

_{MACR0llllllllllllXl}

_llllll

IENTERGROUP _{MACROllllllll:}

llllllllll

llll:

FILEDEFlllllllllllllllll|l:llll

llKEY pROCEDURESll

llllFIELDINDExllll

MACRO OPERATIONSI

(24)

A-14 OPERATIONAL ORIENTATION _DataFlex 2.0 _User's Manual ———————

THIS PAGE INTENTIONALLY LEFT BLANK

(25)

---

A-15

===""===————————————~———

—

——

~—_""""""

"",

ÉÉÉÉFáááEE _OPERATOR'S GUIDE ==========

—~~———

,",

—————

The _objective _{of this} _{section is to provide} a clear, non-technical

summary of use of the system for data entry. The

_first

_{part of the}

chapter will define the procedure _to use DataF1ex for data entry and

file

maintenance. Second1y7 _{the features} and

_facilities

_that may be used _in any given application will be discussed.

DataFlex uses a set of command keys, _called "F1ex-Keys% _{to execute} many of the regularly used _functions In an application software

system. Example _{Flex-keys are} FINDo used _{to locate} a record in the

data base; SAVEJ used _{to store} a new record in the data basep etc.

Furthem since DataFlex is used _on such _{a wide} _variety _of systemsg

especially terminals, we

will

address functions of the program by

their Flex-key name in the course of our discussion, rather than by the _particular key on _{your terminal} which has been established, since

the location of that command key may _vary from system to system. The SETSCREEn

_Utility

_is used _to assign _the DataFlex _Flex-key commands

to a set of control or function keys on _your keyboard. _{Part of}

_its

operation is to print a

list

of the commands and the keys _to which

they are currently assigned on _{your terminal.}

If

you do _not have a copy _{of that}

_list.

go to the SETSCREEn Program ñOWx and _print one for

use with this chapter.

FUNCTIONAL OVERVIEW

A _{DataFlex application} _that _involves data _entry has _{the capacity to} accept data from _the keyboard, check _to make sure that

_it

is the proper type of data. and then _store

it

on _{the computer's floppy or} hard _{disk storage device.} Once data _{is stored,} DataFlex can be made

to retrieve (FIND) _the data and _display

_it

on the CRT, and _{allow the}

operator to change or delete

_it.

All of the capabilities of DataFlex may _or may _not be used _{in every}

application. For examp1é» _{the option exists} _within a configuration to

lock an operator out of a particular data window on the screen _{or to}

automatically make _calculations _that are routine in the process of certain data _{entry situations.} Our _point _{is that although all} _of DataF1ex's _capabilities _will be discussed hereg you may not see

all

of

them used _in every application which you run on _your computer.

(26)

A-16 OPERATOR'S GUIDE DataF1ex 2.0 _User's Manual

+

? DEFINITION OF TERMS

Control Key: A key board _{entry that} _Is made _{while the "control"} key _{is held} down. _Variously _represented as "A _or CTRL A _{to indicate} _that the _control key _{is being}

held while the "A" is also pressed. Flex-key functions can be assigned _{to control} keys _with SETSCREEn.

Data _Entry: The _process _{of putting} _new _information _{into the} computer _{through the terminal} keyboard.

Ffle Maintenance: The _examination, _{changing, or deletion of} infor-mation _that _{is already stored in the} computer.

Fill

Character: A _character _{displayed in} _a "window" (see below) which _{defines the length of the} data _field which can be _{entered or displayed at that particular}

position. Genera1]yg _{the underline} _character ( ) _is used _{for this} purpose.

Function Key: A _special key on the terminal keyboard _that _is

outside of the normal _{typing array.}

_It

_generates _a coded _signal _that can be _"trapped" by _{DataFlex to} execute one _{of the DataFlex Flex-key functions}

(e.g.. FIND, DELETEg SAVE, _etc.). Terminal

function keys _{generate characters that} do _not

display on _{the screen.}

Index: An _organized

list

of keys which _{is linked to the}

records in a

_file.

The index _{fs maintained in}

order automatically by _DataFlex so that records can be accessed _sequentially _even though _the data _is

entered and _stored randomly _{in the} data base. Key: An element _of data _in a record by which _{the record}

can be accessed _{or "found" in the} data base. _E.g.8

the "ACCOUNT NUMBER" _and/or "ACCOUNT NAME" _could be

defined as keys _for _an accounts _receivable _record;

the "ITEM _{ID" and/or} "DESCRIPTION" _could be keys

for an inventory record.

Key _Field: The _fie1d(s) _in _a data _record which _contains _a key.

Key _List: Same as Index.

Window: An _area _{of the} CRT _display _{defined to} accept or

display data. Windows can be _{defined to} accept

only certain types of data... _e.g. numbers _only.

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

~

(27)

DataFlex 2.0 _User's Manual OPERATOR'S GUIDE A-17 —-——————-—————— HOW TO BEGIN

Data _entry and

_file

maintenance _are begun by _selecting _the proper

option from the system menu. All that you need to do _{is select the} number _{of the} menu item for the data _{entry configuration} _that you wish

to execute.

DataFlex screens _{are operated} by the Flex-key commands which you (or the operator) issue(s) from the keyboard. The commands are assigned to certain keys _(e.g. TÁÉJ9 LINE FEED, DELETE, RUB-OUT, _etc.). _function keys _(FL F2,

_etc.k

_{and/or control} sequences ("Áp "Bp etc.) for your

particular system. _This assignment _is done _with the DataFlex

config-uration

_utility

called SETSCREE. Once _the assignment _{of the} commands

is made _{to the various} keys on _{your terminal,} all DataFlex _screens

will operate exactly the same regardless of the fi1e(s) being pro-cessed _{or the format of the screen.}

This feature of DataF7ex promotes _{operator efficiency} and reduces _the

opportunity for errors since there is a procedural continuity

through-out the systan. The _{execution of the} commands soon becomes second

nature so that when a new _{or altered} module is added to the system, no

additional training or familiarization is required.

DataFlex screen _{displays are "active",} which means they can execute

data _entry or

_file

maintenance _functions _at any time that a Flex-key

command _{is issued.} For example,

if

a particular screen contains twenty display

windows, _{but only the}

_first

_five elements _of data are to be

entered

_initially,

then a SAVE command can be issued _after _the

fifth

data item _{is entered.} _This makes

it

unnecessary _to

strfke the RETURN key _after each _{of the blank fields} _just _to

exit the screen. This feature can improve data _entry

effi-ciency by _{substantially} _{reducing the} number _{of keystrokes}

required.

(28)

A-18 OPERATOR'S GUIDE DataF1ex 2.0 _User's Manual

———

—————

FLEX-KEY SUMMARY cnMMANp

ESCAPE _{Terminate the} ENTER _{Program return to} menu. CLEAR _{Clear all} screen windows

RETURN _{Terminate entry in the} window where _{the cursor}

is currently located and move _{cursor to the}

first

position of the next window. .

BACK FIELD Move _{the cursor} from _{the current} window back

to the previous display window on _{the screen.} FIND Find & _{display the record} which _{is associated}

with the key _{in the} window where _{the cursor is}

currently positioned.

_If

there is no data in

the WindOWg _find and _{display the record} which

is

_first

key _{in the} index _{for the field}

asso-ciated with the current window.

SUPERFINO On a screen display which _contains data from

multiple

_files,

this command

_will

_find a

record by _whichever key window _{the cursor is}

currently positioned in. Them _{the related}

records to the keyed _record

_will

be found and

displayed to

_fill

all data windows on the CRT. SAVE _{Stores the displayed} screen information to the

data base.

_If

_the screen contains data from more than one fi1ep data _will be _written _to whatever

_files

_{are part of the configuration.} DELETE Removes _{the dfsplayed record} from _the

_file

and

its

key from _the key

_list.

A _record must be found _before

it

can be _deleted. PREVIOUS RECORD Finds _{the record} whose key _immediately

precedes _the key _{in the} window where _the

cursor is currently positioned.

NEXT RECORD Find _{the record} whose key _{immediately follows}

the key _{in the} window where _{the cursor is}

currently positioned.

CALCULATE Performs _{the calculation} _indicated by _the

expression entered. Calculations can be per~ formed _in a data window9 as well as on the

prompt _line _{of the} CRT.

HELP _Display HELP _screen.

Window _Edit Move _{cursor or} change data _in an image window.

—————————

(29)

DataFlex 2.0 _User's Manual OPERATOR'S GUIDE A-19

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

KFYF'QFf'P coMMRNn _fxf'l ANpTTnN.s ESCAPE

When _the ESCAPE command _{is issued} from _the keyboard, DataFlex

immedi-ately begins _the process of "shutting down _operations". _All open data

files

are c1osed7 and _{the control} _{is returned to the} menu.

It

is important to note _that when _the ESCAPE connand _is madep any data which

is currently displayed is not acted upon in any way unless the program

internally executes a set of commands. _{Specifica11y9}

_if

a new record

has been _{entered, but} not SAVEd _{to disk(ettek} ESCAPE

_will

not _execute

the SAVE command as _{part of its} shut down. _{This also applies} _{in the} case of a changed _{or edited record:}

if

a record is found and _edited

but not re-SAVEd, no change

_will

be made _{in the} data base. CLEAR

The _function _{of the} CLEAR command _{is very simple...} _to erase any data

from the _display windows _(only) and _place the

fill

character in

_all

data window _positions. CLEAR has no effect on data stored in the data base whatsoever;

it

is solely a screen operation. CLEAR can be used as a "bailout" procedure _{during ed¶ting.}

_If

a record has been _called

to the screen (found), and an edit made _that _{is not correctp} CLEAR

will erase the screen and preclude the bad edit from being written to

the data base. RETURN

The RETURN command _terminates data _{entry in} one display window and moves _{the cursor to the next} window. This command is almost always assigned _{to the} RETURN

or ENTER key of your terminal.

If

you _{are entering} datag and _the RETURN command _{is issued at the} end

of the last window on the screerg the _{displayed information} _will be

automatically SAVEd _{in the} data base.

If,

during data _entryg you wish _{to skip over} a window and not enter

any datag simply execute the RETURN command prior to entering any

data.

_If

the window accepts alphanumeric data the _field _will be _given

the value of a string of spaces _that is the length of the window.

_If

the window accepts numeric datá» _{the field} _will be _{set to zero.} DataF1ex can be made _to do an "auto-return" at the end _of a data

field.

This means that when _entered data _completely

_fills

a windowp

the RETURN command

_will

be executed _{automatically.}

_If

"auto-return"

iS "OÑ"p the _{cursor will} jump from the end _{of the current} window

_to

the beginning of the next window as soon as the current window _is

filled

with data. The use of this feature is up _{to the} user and

configurator.

_It

is turned "ON" _with the SETSCREE

_Utility

program.