Re: Query management forms -- MIDRANGE-L

I see what you mean, Vern.

If users want column headings for the queries to use in Excel I always use
a UNION to create the headings and DIGITS the numeric values in the
original resultset.

Perhaps a way to go, ouputting to the IFS instead of printing.
Let the users print it via a Windows apps.

With regards,
Carel Teijgeler

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

On 26-1-2010 at 11:16 Vern Hamberg wrote:

Dean

I've used the print text technique, in fact am doing so in one of our
products. Did you actually print it to a printer? When I did so, it put
the date and page number on the overflow line of the page (60) and the
print text on line 62 - printing to a PC5250 printer session, it didn't
run over to the next page.

What is your QPQXPRTF printer file defined as? Mine is 66 rows, 80
columns, overflow at 60, 6 lpi, 10 cpi.

So I didn't see in the actual printout the behavior you describe - yes,
print text goes 2 lines past the defined page size.

Curious here!
Vern

Dean.Eshleman@xxxxxxxxxxxxxx wrote:

Hi Peter,

Your suggested method is what I was trying to do. The problem I was
having was how to create the QM form. Since these are ad hoc queries,

the

columns would need to be determined at runtime and I don't know how to
create a generic form that would work. That is why I posted my message.

I

was hoping someone could describe how to define a generic form, if that
was even possible. It sounds like it wouldn't work based on the

responses

so far.

By the way, I did try the Print text parameter suggested by Vern.
Unfortunately, it didn't work very well. The Print text overflowed onto

the next page since it was trying to print it at the bottom of the page
and there wasn't room for it. Back to the drawing board.

Dean Eshleman,
MMA, Inc.

On Mon, 25 Jan 2010 16:49:17 -0800, in midrange.midrange-l you wrote:

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

with

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

first

option 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

query

to 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

would

require using a query management report form. Our SQL command

allows

you

to specify the form to use. Normally, we use the *SYSDFT value.

According

to the help on STRQMQRY this means it creates a form on the fly and

uses

that. Does anyone know how to define a form where the heading

would

be a

variable 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

the

Query Management Programming manual, it isn't apparent to me what I

need

to 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

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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

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.

______________________________________________________________________
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.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

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.