Re: Modular advice

Tony,

Unfortunately, you do not tell what the files to be checked have for format. 
What do you mean with "Model" record? I would have the answers in a seperate 
file, layout: filename, field name, expected answer.  

So I take a wild dab at your intensions

So you can use a EXTFILE USROPN file name in part one, using the List Fields 
API to list the lay out of the particular file and and extract data from the 
position.

Then for each field you can call another module/(sub)procedure passing the 
field name (extracted from the list) and the entered value (from the record)

Do the checking in that module and have it write (in another (sub)procedure) to 
your outfile.

Hope this may help.

Regards,
Carel Teijgeler

*********** REPLY SEPARATOR  ***********

On 06-01-06 Tony Carolla wrote:

>I am writing a correction/grading program for our training department.  The 
>task I am trying to accomplish is to create an outfile, with >one record for 
>each field that is wrong for a given student and account#.  The file will 
>contain user profile, filename, field name, >account#, student answer, correct 
>answer (two 30A fields).

>So I am trying to reduce code repetition, and use modules to simplify the task.

>For each file, I will have to
>1)  Chain to the record
>2)  Chain to the "model" record

>Then, for each field (differing types/lengths)
>1)  Check equality
>2)  If unequal, set up an output record
>3)  Write

>I am trying to visualize a way other than having a chunk of code for each 
>field, one after the other.  Any advice would be greatly >appreciated.