body image l*

NUMBER VENDNUM

INPUT "ENTER VENDOR NUMBER: " VENDNUM

MOVE VENDNUM TO INVT.VENDOR //Jump _in here REPORT INVT BY INDEX.I

INDICATE SELECT AS INVT.VENDOR EQ VENDNUM

ENOT SELECTI RETURN END.OF.REPORT _{//jump out} here SECTION BODY

----

body commands

----

REPORTEND

Since _{the selection section is} executed _for every record,

_it

should be

kept as small and _fast as possible. Any _{calculation or string}

manipulation which can be accomplished _{outside the selection section}

will improve speed. _Expressions should be _{evaluated outside the}

selection _section,

_if

possibÍe9 and _{the results represented in the}

selection section as numeric _variables. Numeric _{variables are faster} than numeric WindOWSg and _{string manipulation} commands _{in the}

selection section have _{the greatest potential of all types of}

operations to slow down _{execution. Calculations} and _string

manipulations can be done _{in the} HEADER command _sectiom any of the

SUBHEADER command _{sections, or entirely outside} (prior tO) _{the report} macrop as _necessary.

It

is possible to make compound _{selections in reports, with various} AND and OR _{relationships} among _the

_criteria.

Refer _{to the section of}

this manual on "Conditional Execution" for the

_full

range of possi-

bilities.

The _following AND example shows how _all customers _with balances _over $1AOO AND amounts over 90 days due would be _selected

(NINETY_0AYS_AGO _{is a date variable calculated} by _{subtracting ninety} from _the run date _{before the selection section):}

INDICATE SELECT AS INVOICE.DATE LT NINETY_DAYS_AG0 [SELECT] INDICATE SELECT AS CUST.BAL GT 1000

OR _combinations can be _established by _{inverting the} SELECT _indicator

with a NOT, as in the following example, which would _{report all} customers _with EITHER balances over $1AOO OR balances _over 90 days

old:

INDICATE SELECT AS INVOICE.DATE LT NINETY_DAYS_AG0 [NOT SELECTJ INDICATE SELECT AS CUST.BAL GT 1000

The GROUP ANY/ALL AND/OR ANY/ALL

_facilities

can also be _{utilized in}

setting the SELECT _{indicator for your particular requirements,} as

described in the section of this manual on _indicators.

_———————"____"___

"___"""""

DataFlex 2.0 _User's Manual REPORTING AND OUTPUT C-41

PAGE CONTROL

Page _{control is} handled _{with three predefined variables:}

PAGEFEED _{offers three} way control of how _the page eject will be

determined: -1 " single sheet; O = hardware _{formfeed; or} ## =

linecounter where ## _{is the total} number _{of lines} per page (physical

page height from _{perforation to perforation).} The command _with no argument _{is interpreted} as though _its argument were O _(FomFeed). PAGEEND _{contains the} number _{of printable lines} per page. The _default

is 55. A _{value of} zero (O) _{in this variable}

_will

cause continuous output with no page breaks. This is useful, for examp1e3 _{for output}

to a data

file

from which

it

is not intended to print directly. LINECOUNT _{contains the} number _{of lines output} as of any given moment. There _{Is not normally occasion to manipulate or reset the value of}

this variab1ep since

_it

is used by _the two _{others listed} above. These _{variables are global to Dataflex.} They may be used _with any

kind of outputting, not exclusively under _the REPORT macro. Use MOVE commands _{to put the desired values Into} these _{variables for} page

control immediately before the REPORT command.

This example _{illustrates operator-entered selections} and page control:

C-42 REPORTING AND OUTPUT DataF1ex 2.0 _User's Manual

/PROMPT

List NAMES from which STATE:

_

/HEADER

NAMES FROM STATE OF:

_

...NAME _..

_...CITY...

/B0DY

l*

FORMAT PROMFT.I {CAPSL0CK} STRING TEMP _I

ACCEPT PROMFT.I

_//

_{get operator input}

CLEARSCREEN QUTFILE 'CON:

'

//

output to the screen

OPEN LIST _I

MOVE 22 TO PAGEEND

_//

page length is # _{of lines} on screen MOVE

_-I

TO PAGEFEED

_//

_{stop at the bottan of} each screen REPORT LIST BY INDEX.I

_II

REPORT command

INDICATE SELECT AS LIST.STATE EQ PROMPT.I SECTION HEADER

PRINT PRQMF'T.I

_//

_{print state selection to} heading OUTPUT HEADER

SECTION BODY

PRINT LIST.NANE

_//

_{print data} PRINT LIST.CITY

OUTPUT BODY REPORTEND

INPUT "PRESS RETURN TO CONTINUE" TEMP ABORT

OUTPUT DESTINATION

Unless _{directed elsewhere, the default output device for the} REPORT macro is the system I-ST: _{device (printer).} Output can be _redirected

to any valid sequential system device or

file

by placing an argument on the operating system command _line wheA _{the configuration is} executed (FLEX _{report destination). This} form _of command can. of

courseg be _{included in} menus for operator selection, with or without querying for filename or device input. A1ternat1ve1yp _{the output}

device or

_file

can be _"hard coded" _{in the configuration} on the QUTFILE command _line fmmediate?y above _the REPORT command _line. Used _{in this} way9

literal

destinations ("CON:

",

'NERGFILE", etc) must be embedded

in quotation marks. Arguments _without quotes

_will

be _considered

string variables, which _can be used _{to pass operator input in} response

to query prompts _{at the beginning of the configuration.} Legal

devices on most systtms include CON: (CRT screen), PUN: (often used

for modemsL (-ST: _{(the printer).} and any legal filename.

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

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

DataF1ex 2.0 _User's Manual REPORTING AND OUTPUT C-43 ———————————— =—==———————~

OPERATOR ABORT

The REPORT macroG _default mode _{of operation} causes a report to abort

if

any key _is

_hit

by _{the operator while the report} is executing. This

mode may be _{disabled entirely or modified to} ask _{the operator} a

confirming question when a key _{Is thus}

_hit.

To do _{this» provide} a

substitute for the predefined subroutine called "RPT.KEYPRESS'4

optimally just before the REPORTEND command. The _i1lustrat1ve

subroutine below would _{give the} prompt "PRESS <ESC> TO ABORT, ANY OTHER KEY TO CONTINUE", and _then, depending on which key was pressed, either resume _{execution at the predefined procedure} "RPT.LOOP" or abort via the predefined procedure "END.OF.REPORT". (Pressing any key

other than ESCape _actually would cause execution to resume.) EXAMPLE:

RETURN

_//

Must be added _after end _{of section} commands RPT.KEYPRESS:

STRING PAUSEKEY

_l

INPUT "PRESS <ESC> TO ABORT, ANY OTHER KEY TO CONTINUE" PAUSEKEY [KEY.ESCAPE] RETURN END.OF.REPORT

RETURN RPT.LOOP

This procedure should be _{located before the} REPORTEND command, and

immediately after the end _{of the last} group of section commands, The RETURN command shown above on the

_first

line must be added _explicitly

in the configuration in order to insert this procedure.

If

the predefined procedure END$0F$REPORT _is used _{instead of} END.0F.REP0RTg _tota11ing and _{other terminating} procedures would be

skipped. Use _{of this} procedure would be _{appropriate to} use in case of printer misfeed, ribbon breakage, _or a similar mishap.

PAGE BREAKS

The REPORT macro automat1ca11y maintains the number of lines remaining on the current page in manory at all times while outputting.

_It

will

handle _{things like} number _{of lines required} by a SUBTOTAL _or BODY image automatically, and

if

allowed to operate in

_its

default mode,

it

will

reprint headings and subheadings as required at the top of each new page.

_If

you are doing _"fancy" pagfng _{that requires direct}

controb howevem you will have _{to provide} commands _{within the} appl1cab1e _{section(s) (typically the} BODY). The PAGECHECK command checks whether _the number _{of lines} given _{in the} command argument remains on the current page. The FORMFEED command sends a "raw" formfeed _{(that is,}

_it

does _{not print} headings _{at the} top _{of the} new

page). The sequence [PAGEBREAK] GOSUB NEWPAGE utilizes the PAGEBREAK

predefined indicator and _the NEWPAGE _{predefined procedure to print} headings _{at the top of the} new page. The _following commancb _for examp1eg would _{eject the current} page and _print headings _{at the top of}

C-44 REPORTING AND OUTPUT DataF1ex 2.0 _User's Manual

the next page

_if

there were less than 6 _lines

_left

on the current page:

PAGEQIECK 6

Cpagebreak] GOSUB NEWPAGE

The _following command would do _the same thing unconditiona11y:

FORMFEED GOSUB NEWPAGE

REPETITIVE REPORTS

A _report can be put _in a loop _to execute _{multiple times for different}

selection

_criteria.

Put a label at the beginning of the report and

then, at the end _{of the reportp} CLEAR _{the report} data

_file

and GOTO

the label at the _{beginíng of the report.} Remember _{to provide} some means for the operator to exit the loop.

MULTIPLE COPIES:

To make _{multiple copies of} a _report you must: _{(I) set your} OUTFILE _to a disk

_file;

and (2) _{print that}

_file

_{multiple times.}

OUTFILE "TEMP.$$$"

_//

_{Output to} temporary

_file

REPORT X BY INDEX.I

_//

Do _report

----

REPORTENDreport

---

//

The _{following lines print the disk}

_file

multiple times DIRECT_OUTPUT "LST:

"

//

Output _{to printer} INTEGER COUNT

SIRING STRVAR 132

//

You must have _set up NUMBER 0F_COPIES _previously. FOR COUNT FROM

_l

TO NUMBER OF_C0PIES

DIRECT_INPUT "TEMP.$$$" [NOT SEQEOF] REPEAT

READLN STRVAR

_//

Reads _{a line} from TEMP.$$$ WRITELN STRVAR

_//

_{Writes a line to the printer}

[NOT SEQEOF] LOOP

_//

End _of REPEAT loop

FORMFEED LOOP

li

End _of FOR _loop

CLOSE_INPUT

_//

Close _{before delete}

ERASEFILE "TEMP.$$$"

_//

_File no longer needed

DataFlex 2.0 _User's Manual REPORTING AND OUTPUT C-45

"",_

~

THINGS TO REMEhdER ABOUT THE REPORT MACRO

l.

The REPORT macro may be used _only once within a configuration. e

2. The maximum _{line length} which can be output is 255 _characters.

3. Fields used as subtotal breakpoints must be _indexed. They can be

in the main

_file

_{or in} any other RELATEd

_file.

4. Subtotal and _{total registers are} updated _only by PRINT commands; MOVE, CALCULATE and DISPLAY do not update _{the registers.}

5. Data should be processed _only from database elements

or in-memory variables. The _{contents of formatted} windows cannot _re?lab1y be used

for calculations or other processing.

6. An _invisible AUTOPAGE command _is executed _{at the beginning of} each command _section. and an invisible RETURN command _{at the} end.

7. The BODY _{section of the report is} executed once for every record

which _{satisfies the selection}

_criteria.

REPORTING WITHOUT REPORT

The usual way of configuring reports is by use of the Report macrcn

often starting with the QUERY program _{to generate} the _{configuration.} The Report macro, howevem _is by no means the only way of configuring reports--it is merely _a pre-programmed convenience _{suitable to} a wide range of purposes. The following configuration outputs a data

_file

(called SAMPLE _{in this} example) _to the _{printer in record} number sequence, _using a format image _with a pagename of IMAGE. Note _that

it

lacks headings, totals and _subtotals commonly found _{in reports} produced by _the Report macro.

/IMAGE

l*

OUTFILE °'LST:

"

//Direct output to the printer

OPEN SAMPLE //Open _the data

_file

_{to output}

CLEAR SAMPLE _{//Clear the record buffer}

CLEARSCREEN _{//Clear the} screen

REPEAT

FIND GT SAMPLE BY RECNUM _{//Find the next record} by number IF0UNDI BEGIN

PRINT SAMPLE.NAME TO IMAGE.I _{//Must state} TO PRINT SAMPLE.CITY TO IMAGE.2' _{//Window.# since} PRINT SAMPLE.STATE TO IMAGE.3 //AUTOPAGE command PRINT SAMPLE.ZIP TO IMAGE.4 _//not used

OUTPUT IMAGE END

[NOT SEQEOF] LOOP _{//Stop at} end _of

_file

ABORT

C-46 REPORTING AND OUTPUT DataF1ex 2.0 _User's Manual

—

——

.

THIS PAGE INTENTIONALLY LEFT BLANK

—————————

ZZZ±ZTZZZZ±ZFF2:

_{ZZZ::2:::7:::::::7:::7:::::::---}

_- C-47

========== =========

ZZZZZZTZZZ FILE DEFINITION (FILEDEF) _=Z======

========== == —=_—___—

——————— OVERVIEW

The FILEDEF

_utility

enables you to create a complete

_file

_definition

for data base

_files

used _in a DataFlex application. The

file

definí-

tiom once created, contains information about _the

_file

namep indexed

fieldm and _{field information.} Each _DataFlex

_file

must have _certain

information about _{the structure of the} data?

_file

_name, indexes _etc.,

established before

_it

can be used. Once donm _{this information}

_is

avai1ab1ep _{through the} data base managéí"» to any DATAFLEX program.

During execution, the programs can _{adjust thei r operation to the type} and _{length of the}

_files

and _{fields in} use. This gives DataF1ex

_its

unique APPLICATION INDEPENDENCE.

APPLICATION INDEPENDENCE means that the same data

_file

can be used _in

multiple applications without the duplication of effort and _storage found _In most _conventional application programs.

EXAMPLE:

We may want _to implement accounts _receivable, accounts payable and a

mailing

_list.

Instead of having _three

_files

_with name and address

informatioñ» we could have one name/address

_file

which _{is referenced} by _{all three applications.} Only _this one

_file

need be _{defined, stored} and updated _for names and addresses, _{thus saving} both _time and

storage... a real bargain!

Because these data base

_files

_{potent1a1ly are} so integrated with the

total application picture, thought and _care should be _{put into the}

contents and _{eventual relationships of the}

_files.

A _{well-designed}

file

structure will almost automatically mean an effective and

successful app1 _ication.

~ _{~ —————————————————————————————}

C-48 FILE DEFINITION (FILEDEF) _DataFlex 2.0 _User's Manual "=============———————————————————

—

STEP ONE

In document DataFlex V2 Jul1984 pdf (Page 152-160)