Re: Query management forms

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Carel

I like that idea, too. If I understand, you convert numerics to alpha. I 
forget, does digits give you the decimal point and the sign? If not, 
maybe a CHAR() cast is in order.

As an extension that might work - let me see - put the data out in full 
rows - one long field per - and put heading information there first, 
followed by column headings, then data rows. Main issue I see is lining 
up the columns - SQL tends to strip trailing blanks in my experience. 
This could be butt ugly, since it'd require lots of functions, leading 
to lots of table scans - Yuk!

OK - that was probably not a good idea!!

Later
Vern

Carel Teijgeler wrote:
> 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