Generación de nubes de puntos para superficies y volúmenes, algoritmo de rellenado de

._

TOTAL PURMASES: $

._

LAST PURQUiSE:

_{_J_J_}

Data _in < > can be used _to FIND vendors

l*

OPEN VENDOR

_//

_all

_files

must be opened. ENTER VENDOR

_//

_{inltalize enter} macro.

AUTOPAGE FORM

_//

_{automatically assign} windows ENTRY VENDOR.RECNUM {NOPUT,AUT0FIND}

//

Translatiom Do data _{entry with the record} number _{of the} vendor

_file

//

automat1ca11y _{find record,} do _not update _{the record buffer since}

//

record number _can't be changed. ENTRY VENDOR. VENDOR

//

Translation, Do _standard data _entry on the vendor name of the vendor

_file.

ENTRY VENDOR.ADDRESS

ENTRY VENDOR.CITY ENTRY VENDOR.STATE ENTRY VENDOR.ZIP ENTRY VEND0R.NONE_AC ENTRY VENDOR. PHONE

_

EXOlG ENTRY VENDOR.FHONE

_NUMBER

ENTRY VENDOR.TERMS ENTRY VENDOR.CREDIT_ LIMIT

ENTRY VENDOR.CREDIT _USED {DISPLAYONLY}

//

Translation, When _the vendor

_file

_is FOUND, _{display credit} used _{in this}

//

window.

ENTRY (FORM.II-FORM.12) {DISPLAY0NLY}

//

Translation, When a record is founch _{display the result of the calculation}

//

of credit

_limit

(FORM.II) minus _credit used (FORM.12) fn _this window. ENTRY VENDOR.PURMASES {DISPLAY0NLY}

ENTRY VENDOR.LAST_PURMASE {DISPLAYONLY}

RETURN

_//

_return from _{entry section}

ENTEREND

_//

end _{of enter} cormand

ABORT

_//

_{stop after} escape key.

//

note: the entry command can only be used _inside an _{enter or entergroup} KEYPROC KEY.USER

_//

_{Define action of user defined} key

OUTPUT FORM

_//

_{Output the} page

ENTAGAIN

_//

_{Return to} same window

RETURN

———————

DataF1ex 2.0 _User's Manual SAMPLE APPLICATIONS C-81

————— —

Notice the similarity between _this

_file

and _the one for CUSTOMERS. Each ENTRY connand _{line links} a data base _{field with} a WINDOW. Close _{to the bottom.} we see something new: ENTRY (F0RM.I1-F0RM.12).

This is a calculated field that translates to:

WHEN DISPLAYING FILE 21, SUBTRACT THE VALUE OF WINDOW 12 (FORM.12) FROM THE VALUE OF WINDOW

li

(FORM.ll) AND PUT THE RESULT IN WINDOW 13.

There _{is not} a report for the vendor

_file

_{supplied with the} sample

configurations; this one is up _{to you.} Create a report format for

VENDOR and use the CUSTOMER _report as a model. After making _the

report, add

it

to the MENU _{using the} MENUDEF program.

After.making your reportg try your hand at a simple

file

definition and _{configuration using the} AUTODEF Program. AUTODEF _takes a screen IMAGE _{format created with} a _{text editor} and makes both _the

_file

definition and _{compilable configuration}

_file

from

_it.

_After making thesep _{look at the}

_file

_{definition with the} FILEDEF program and _type

out the configuration with the operating system TYPE command. Then

compile the _{configuration.} THE INVENTORY FILE:

With _{the inventory}

_file

we start to see the true power of DataF]ex.

Each _{inventory part is supplied} by a VENDOR, so the INVENTORY

_file

_is

said to RELATE _{to the} VENDOR

_file.

When an inventory part is found

(called into memory), _the RELATED VENDOR _{record automatically} comes

with

_it.

This relationship is automatically maintained by _DataFlex.

DATA ACCESS CORPORATION INVENTORY MASTER FILE

—————— VENDOR NUNBER:

_

.

NAME: VENDOR PART ID:

YOUR PART ID: DESCRIPTION: STOCK QUANTITY: . MINIMUM QUANTITY: . REORDER QUANTITY: . QTY ON ORDER: . SALES/MONTH: $ .

_

SALES/YEAR: $

._

PROFIT/YEAR: $

._

LIST PRICE: $

._

WHOLESALE PRICE: $

._

AVERAGE COST: $ .

_

STOCK VALUE: $

._

——————— —

C-82 SAMPLE APPLICATIONS _DataFlex 2.0 _User's Manual

— —————

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

When _{running the inventory} data _{entry screen, the}

_first

two _fields are

actually out of the VENDOR

_file.

You can find the vendor _{of interest} on this screen by _either keyp _{just like} you could in the VENDOR

screen. You can then move _{the cursor} down _to VENDOR PART ID: _{to find}

the

_first

(or any) _{part for that vendor.} The vendor number and then

vendorG part number make up a "two segment _{key", that is,} you must

find the vendor, _{then, put in all or part of the} vendors _part number

to find a record by that index. To find the

first

part for any vendor, _{enter the} VENDOR NUMBER _or NAME and

_hit

_the "SUPERFINO" _key. The INVENTORY

_file

_{is also} indexed _{(able to find records} by) "YOUR PART ID" and "DESCRIPTION". You can put _{the cursor in} any _of these windows and _find a particular partt

When you are creating a new partg find the vendor _firstp then

fill

In

the other windows _like you _{did in the other screens.} This configura-

tion will also allow you _{to create} new vendors from this inventory

screen. Just enter a new vendor name with no vendor number, and when you SAVE the partg a new vendor _will be _{created. Later} we

will

see how _{to disable this feature}

if

you want.

DataF1ex 2.0 _User's Manual SAKPLE APPLICATIONS C-83

INVENTORY FILE DEFINITION:

FILE DEFINITION LISTING FOR FILE #22

***************************************************

FILE ROOT NAME = INVT

USER DISPLAY NAME = INVENTORY FILE SHORT NAME = INVT

***************************************************

RECORD LENGTH _- 128 (USED ₌ 104) MAX NUMBER OF RECORDS ₌ lOó (USED _{= 33)} DELETED SPACE IS REUSED

MULTI-USER RE-READ ACTIVE

***************************************************

FIELD FIELD FIELD FIELD DEC MAIN RELATES--TO NMBR OFFSET LEN TYPE PTS INDEX FILE FIELD

---

————-— _-—--- -—-—-

_---

-——-- -—-— _-—---

I

_l

2 NUMERIC O

_l

21 O VENDOR

2 3 15 ASCII

_l

O O VENDOR PART_ID

3 18 15 ASCII 2 O O PART_ID 4 33 35 ASCII 3 O O DESCRIPTION 5 68 3 NUMERIC O O O O QUANTITY 6 71 2 NUMERIC O O O O MINIMUM 7 73 3 NUMERIC O O O O REORDER 8 76 3 NUMERIC O O O O ON_0RDER 9 79 5 NUMERIC 2 O O O SALES_M0NTH

10 84 5 NUMERIC 2 O O O SALES YEAR

II

89 4 NUMERIC 2 O O O PR0FIT_YEAR

12 93 4 NUMERIC 2 O O O LIST_PRICE

13 97 4 NUMERIC 2 O O O WH0LESALE_PRICE

14 101 4 NUMERIC 2 O O O AVG_C0ST

INDEX

_l:

FIELD SEGMENTS: <1> <2> INDEX 2: FIELD SEGMENTS: _. <3>

INDEX 3: FIELD SEGMENTS: <4> <0>

The

_first

_field "VENDOR NUMBER" RELATES _{to the record} number

_(field

zero) of the vendor

_file

_{(#21). This is all that's required to} RELATE

the inventory

_file

to the vendor

_file

and

it

essentlaily makes _the vendor

_file

a logical extension of the inventory

file.

The INVENTORY

_file

has THREE _indexes. The

_first

index _is by vendor number _(field one) AND vendor _{part id (field two). This} combining _of

fields to make one index _{is called} a multi-segment index. Since

record number _is NOT appended _{to this index,} two _{parts Cáñft} have the same vendor AND _part number, which would be a duplicate record.

Index TWO _is on field 39 or YOUR PART ID, a1lowing _the same _{part to} be known by two _{different part} numbers, _yours and _{the vendoMs.} Could two _parts have _the same part number?

_If

notp how _could you allow that

if

you wanted? Answer: No, two parts could not have the same number, but

_if

_they coulcb _{the circumstance could}

_still

be _{dealt with}

effectively by appending _field ZERO _{(the record} number) _{to the indem}

rendering the composite index _entry unique _{despite the duplication.} Index THREE _allows access by DESCRIPTION. _{Notice the} "MAIN INDEX" column _{of the}

_file

_definition. The main index _{is the} number _{of the}

C-84 SAMPLE APPLICATIONS DataFlex 2.0 _User's Manual

index _{that will} be used when you FIND by _that

_field.

_{In this}

_file

there are no fields that are used _in more than one index, but where

there are9 the main index becomes _important.

THE INVENTORY ENTER CONFIGURATION: (some _{lines are deleted} from _the image area _{to conserve} space) IFORM

DATA ACCESS CORPORATION INVENTORY MASTER FILE

VENDOR NUMBER: <

_

.> NAME: < >

VENDOR PART ID:_<

'

YOUR PART ID: < > DESCRIPTI0N: <

'

STOCK QUANTITY: . MINIMUM QUANTITY: _{_.} REORDER QUANTITY: . QTY ON ORDER: SALES/MONTH: $

._

SALES/YEAR: $

._

PROFIT/YEAR: $

._

LIST PRICE: $

._

WHOLESALE PRICE: S

._

AVERAGE COST: $

._

STOCK VALUE: $

._

l*

//

This enter configuration is a

_little

more sophisticated since

_it

deals

//

with two

_files.

The _inventory

_file

RELATES _{to the} vendor

_file.

OPEN INVT

_//

_All

_files

must be OPENED _before use. OPEN VENDOR

_//

The _{order of} opening _the

_file

_Is

//

not important.

ENTER INVT VENDOR

_//

ENTER

_will

_maintain both INVT and VENDOR.

//

Since INVT _relates TO VENDOR

it

MUST be

// first

on the ENTER line.

//

INVT _{is the} main

_file.

AUTOPAGE FORM

_//

Set up _{to automatically} assign windows.

//

These _fields use the AUTOPAGE _option--the windows are automatically

//

assigned _{to the} FORM page.

ENTRY VENDOR.RECNUM {AUTOFIND}

//

Translation, do data _entry on the record number of the vendor

file.

//

Automatically try to find the vendor by number.

//

Note _{that the} element _{of the related} TO

_file

_is used _here

//

and _{automatically} PUT _{to the} VENDOR _{field of the} INVT _ff1e.

//

The _related TO element should always be used _in a case like this. (This configuration is continued on the next _page.)

DataF1ex 2.0 User's Manual SAMPLE APPLICATIONS C-85 ————— ENTRY VENDOR.VENDOR {SKIPF0UND,FINDRECL}

//

Translation, Do data _entry on the vendor name of the vendor

_file

//

Skip _{this entry}

_If

a record has _already been found and REQUIRE

//

that a vendor be found to continue.

ENTRY INVT.VEND0R_PART_ID {SKIPF0UND,RETAIN}

//

Translation, Do data _entry on the vendor _{part id of the inventory}

// file.

Skip _this

In document Algoritmos de pre y post proceso para métodos numéricos de puntos, métodos de partículas y libres de mallas (página 66-70)