RE: Text on report

Booth Martin wrote:

>Why are you running down an array as a solution?  

At no time did Jim specify anything that could be construed as a
requirements document, so we're all pretty much going wild "designing" THE
"solution."  I'm not sure anybody is really hardcore about any one method...

>If the letter writing is an occasional thing with rare 
>modifications then having the whole piece 
>in one easily found object makes sense.  

Agreed!

>An array at the end of a 20-line RPG program allows 
>green screen full page editing which isn't available 
>any other way without writing a file-editing program 
>and file definitions with all the attending documentation.  

Urm... as long as we're still in brainstorm mode, how about:
CPYF pf qtemp/srcpf fmtopt(*cvtsrc)
STRSEU qtemp/srcpf
CPYF qtemp/srcpf pf fmtopt(*cvtsrc)
  We used this sort of thing a lot when we had trained computer operators
who could understand FMTDTA specs.

>What could easily be a 20-line program suddenly blossoms 
>into a whole application that takes a 1/2 week 
>to write, test, and install.

Programmers just love to add bells and whistles!  Actually, this is a good
call - "time to implement" may certainly be a factor: who knows?

Buck Calabro
Aptis; Albany, NY


Billing Concepts Corp., a NASDAQ Listed Company, Symbol: BILL
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---