RE: Changing variables &1, &2 in a message text

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx / Mike Barton
>
<snip>
>
> Alternatively, you can as suggested change the message text ID.
> Best way to do this is not to change the actual system message but use an
> override instead:
> CRTMSGF    MSGF(QTEMP/QQRYMSG )
> ADDMSGD    MSGID(QRX1905) MSGF(QTEMP/QQRYMSG) MSG('Select parms here')
> OVRMSGF    MSGF(QQRYMSG ) TOMSGF(QTEMP/QQRYMSG )
> now run query
> again, havn't tried this so cannot vouch if it works ok..
>
> HTH
>
> Mike

Wow.  Learn something new every day.

Only thing I would say is that, instead of CRTMSGF, use CRTDUPOBJ on the
QQRYMSG object so that you get all of the message descriptions.  Then use
CHGMSGD QRXnnnn instead of ADDMSGD.

I just tried this out for myself and it works as has been described, but I
got to thinking about the original message.  If the query is doing the
record selection, why not just type that in on the "Specify Cover Page"
and/or "Specify Page Headings and Footings" within WRKQRY?  How else are
selection parameters outside of the query going to affect the results of the
query?  Is the queried file being build on the fly prior to the RUNQRY, same
format as the file the query was created with?  Or is this running the query
using STRQMQRY ALWQRYDFN(*YES) SETVAR((PLANFROM &PLANFROM ) (PLANTO
&PLANTO))?

Somewhere along the line, it becomes easier / more efficient / faster to
work with to drop it (the report) from query, pull the SQL from it and put
it in an RPG program.  Query was never meant to be a be-all, end-all data
reporting tool.

It's been awhile, but isn't it possible to manipulate the headers in a
QMQRY?  Maybe convert the *QRYDFN to *QMQRY (via RTVQMQRY), etc.  I'd go
into it more, but I'm short on time.

hth, db