× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yeah, Carel, that describes the way I've had to handle fields I don't want
to display - put them off the page. Otherwise, I LOVE QM forms.

Regards

Vern

At 11:31 PM 11/21/2002 +0100, you wrote:
Vern,

Sorry for the late reply.

In QMQRY:
Not really, you can indicate BREAKx (where x  is 1 to 9, indicating the
breaking level) or OMIT. I would try to OVRPRTF the SPLF of QMQRY a liitle
smaller than the report length and place the Token field at the end. It
may then produce two SPLF's,and the last one can be removed. (Default page
width is 80)

QMQRY is part of the SQL Development kit. If it is installed it is on his
system.

We do not have Query/400 on our system, unfortunately. So from memory lane:
You can tell the field to be field 0 in the result set and it will not
print, but it might be used as a break level field at the same time.

It is possible to turn a QRYDFN (Query/400) into a QMQRY object with
RTVQMQY QRYDFN(*YES) and CRTQMQRY using a source file. A form can also be
created with a source file, but that is very trickyand obscure. Midrange
Computing had an article on it, see www.mcpressonline.com.

Otherwise, if the field is on the page, let them ignore it.

Regards,
Carel Teijgeler

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

On 20-11-02 at 16:52 Vern Hamberg wrote:

>Carel, you beat me to it. But he is using Query/400, not Query Manager.
>
>Can you suppress the Token column in the form - it'd be nice not to see it.
>

-snip-




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.