|
Hi Dean,
Another sort of clunky way would be to construct the variable part of the heading, pass it as a parameter to the QM query, and include it as a field and just don't print it with the detail. Then you can refer to it in the QM form heading as &field. It might perform better than doing all the copying.
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /
On 1/25/2010 12:24 PM, Dean.Eshleman@xxxxxxxxxxxxxx wrote:
Vern, you are correct about my requirements. Thanks for the tip regarding
the Print text parameter. I hadn't noticed that before.
The only other option I thought of was to utilize the User defined data
parameter and have the SQL command processing program copy the spool file
to a DB file and then read it and add the User defined data as the heading
on each page. This is a long way around to get what I want, but I think
it would work. I guess I'm not sure what the performance would be though.
Dean Eshleman,
MMA, Inc.
On Fri, 22 Jan 2010 18:41:59 -0600, in midrange.midrange-l you wrote:
Yes, but Dean wants a dynamic layout, the same as the default but withfirst
his own report heading.
I don't think this can be done - too bad.
You might try saying *YES to date/time and page numbers, which go on the
bottom of the page. And for some report description, use the print text
parameter of OVRPRTF QPQXPRTF
HTH
Vern
Carel Teijgeler wrote:
Dean,
STRQM option 1
Edit a query
Press F13 and you can edit your FORM
You can add variables in your heading by referencing the number of the
column in the result set. (so it should be in the SELECT)
Thus "Client:&6" refers to the sixth column in the result set.
You can leave the same column out of the result set by selecting the
queryoption and use the option OMIT.
This was a quick "101"
With regards,
Carel Teijgeler
*********** REPLY SEPARATOR ***********
On 22-1-2010 at 16:49 Dean.Eshleman@xxxxxxxxxxxxxx wrote:
Hi,
We have an interactive SQL command that utilizes a query management
wouldto execute the SQL statement. When we specify *PRINT as our output, I
would like to be able to specify a report heading. I assume this
yourequire using a query management report form. Our SQL command allows
Accordingto specify the form to use. Normally, we use the *SYSDFT value.
usesto the help on STRQMQRY this means it creates a form on the fly and
be athat. Does anyone know how to define a form where the heading would
thevariable and the columns would be determined at runtime? Do I need to
figure out how to create the form on the fly myself? I have looked at
needQuery Management Programming manual, it isn't apparent to me what I
notto do. TIA
Dean Eshleman,
MMA, Inc.
______________________________________________________________________
Confidentiality Notice: This information is intended only for the
individual or entity named. If you are not the intended recipient, do
error,use or disclose this information. If you received this e-mail in
soplease delete or otherwise destroy it and contact us at (800) 348-7468
Thankwe can take steps to avoid such transmissions errors in the future.
______________________________________________________________________you.list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information. If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmissions errors in the future. Thank you.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.