Re: Text on report

This brings up a good point, Joel.

How about if I put the text in a message file?

That seems like a logical place for it, after all.  I didnt' think about this, 
but you brought
up a very good point, and looking at your key data, this is almost the exact 
same information
in the key info for a message file.

Any thoughts?

Regards,

Jim Langston

"Stone, Joel" wrote:

>
>
> In addition to the good advice you received about placing the data in a file 
>(and the bad advice about using eval / arrays), I will add my 2 cents.
>
> There will probably be other reports with other text messages.  Pretty soon 
>you will have a dozen files, all for the same purpose.
>
> If you create a file now with a key prefix, you can use the same file for all 
>reports, and write only one maintenance program for them all.
>
> Fields could be something like:
>
> field-name    length
> Msg_Group       10
> Msg_seq         3 numeric
> Msg_data        78
>
> For the application you are working on today, the Msg_Group name could be 
>"PURCH01", Msg_Seq would be 1 thru 12 for twelve lines of text, and the data 
>is 78 long so it can fit on one line of a green screen.
>
> As you add more apps, you can simply add more Msg_Group records.  For example 
>if you need text on an invoice next month, add records where Msg_Group = 
>"INVOICE".
>
> You can add more flags onto the end of the file above too.  For example, 
>maybe you want a flag such as Msg_Public  (Y/N)  so you can have some msgs for 
>internal reports, and other msgs for public (customer) reports.
>
> Also maybe you want a change date and used-id field, so you know who changed 
>the msg and when.

+---
| 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
+---