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


  1.  Home
  2. MIDRANGE-L
  3. December 2005

RE: Big, Honking SQL Statement

Cool. man! The thing I use for the front end is usually a command, not a display file, for Q & D, but either one works. I just got tired of DSPFs in CL some time ago. ;-)
Just a further thing - one thing you can do easily in QM forms is to wrap long text in the width of your column. You can't do this at all in Query/400, and it is possible but not simple with a PRTF. Just take a look at the editing codes for character columns.
OH, and do look at the dreaded Query Management programming guide - there are several tips there, esp. chapter 11. And things about using Query/400 objects in QM. And handling apostrophes. And.... 

Vern

At 05:07 AM 12/8/2005, you wrote:


Thanks Vern...I created a member with said big honking SQL statement and
did a CRTQMQRY. Then I used STRQM to create a QMFORM. Then I put the
STRQMQRY in a CL program, put a display file on the front end to get
some data, and passed the data as CL variables to the QM query. Pretty
darn easy...

> -------- Original Message --------
> Subject: RE: Big, Honking SQL Statement
> From: Vernon Hamberg <vhamberg@xxxxxxxxxxx>
> Date: Wed, December 07, 2005 10:23 pm
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
> I'm with you on QM, Michael. You mentioned getting a good-looking
> report. QM also has forms, which let you define the layout. STRQM is
> the place to create these puppies, unless you are really into pain.
> (See the Query Management programming manual for the syntax of
> *QMFORM source.) You can get to form maintenance using F13 from the
> QMQRY screens.
>
> BTW, you can get the QMFORM equivalent (mostly) of a QRYDFN using the
> RTVQMFORM command. Also, RTVQMQRY pulls out the SELECT-statement
> equivalent of a QRYDFN - with some nasty limitations involving join
> types. But you can get warnings about this. There is even an ANZQRY
> that will let you know about things that don't completely convert
> over from QRYDFN to QM objects.
>
> The other benefit of using a QMQRY is that you can have substitution
> variables. This lets you pass CL variables to the QMQRY, using the
> SETVAR parameter of the STRQMQRY command.
>
> Enjoy!
>
> Vern
>
> At 02:06 PM 12/6/2005, you wrote:
>
> >Thanks to all for the suggestions. I've implemented a QM query for my
> >immediate (tomorrow) need, and will investigate UDFs for the longer
> >term. This QM stuff is pretty cool.
> >
> >
> > > -------- Original Message --------
> > > Subject: RE: Big, Honking SQL Statement
> > > From: michael@xxxxxxxxxxxxxxxxxx
> > > Date: Tue, December 06, 2005 2:47 pm
> > > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > >
> > > Thanks Rob...that seems to be working for me.
> > >
> > > > -------- Original Message --------
> > > > Subject: RE: Big, Honking SQL Statement
> > > > From: rob@xxxxxxxxx
> > > > Date: Tue, December 06, 2005 2:40 pm
> > > > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > > >
> > > > If you do not actually have QM you could always paste that into a source 
> > > > member.  Then do a CRTQMQRY.  From there you can do a STRQMQRY.  The
> > > > STRQMQRY is where you put in the values.
> > > >
> > > > Rob Berendt
> > > > --
> > > > Group Dekko Services, LLC
> > > > Dept 01.073
> > > > PO Box 2000
> > > > Dock 108
> > > > 6928N 400E
> > > > Kendallville, IN 46755
> > > > http://www.dekko.com
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > michael@xxxxxxxxxxxxxxxxxx
> > > > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > > > 12/06/2005 02:14 PM
> > > > Please respond to
> > > > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > > >
> > > >
> > > > To
> > > > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > > > cc
> > > >
> > > > Fax to
> > > >
> > > > Subject
> > > > RE: Big, Honking SQL Statement
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > How can I get an SQL statement into QM?
> > > >
> > > > > -------- Original Message --------
> > > > > Subject: Re: Big, Honking SQL Statement
> > > > > From: FrankKany@xxxxxxxxxxx
> > > > > Date: Tue, December 06, 2005 1:40 pm
> > > > > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > > > >
> > > > > QM will let you get it done quick and easy.
> > > > >
> > > > > Frank W. Kany IV
> > > > > Senior Programmer/Analyst
> > > > > Unipres USA, Inc.
> > > > > (615) 325-8428 - Office
> > > > > (615) 517-1742 - Cell
> > > > > http://www.unipres.com
> > > > >
> > > > >
> > > > >
> > > > > michael@xxxxxxxxxxxxxxxxxx
> > > > > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > > > > 12/06/2005 12:18 PM
> > > > > Please respond to
> > > > > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > > > >
> > > > >
> > > > > To
> > > > > midrange-l <midrange-l@xxxxxxxxxxxx>
> > > > > cc
> > > > >
> > > > > Subject
> > > > > Big, Honking SQL Statement
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Ok...here's my deal.
> > > > >
> > > > > I have this big SQL statement...it does what I want it to do.
> > > > > I need to pass in two parameters (a numeric date and an alpha string). 
> > > > > I need to format the output nicely.
> > > > >
> > > > > What's the best approach? Should I have an RPG program that has the SQL > > > > > statement as a variable and I use PREPARE with parameter markers? Is QM 
> > > > > a better idea?
> > > > >
> > > > > Thoughts are appreciated...
> > > > >
> > > > >
> > > > > --
> > > > > 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.
> > > > >
> > > > >
> > > > > --
> > > > > 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.
> > > >
> > > > --
> > > > 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.
> > > >
> > > >
> > > > --
> > > > 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.
> > >
> > > --
> > > 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.
> >
> >--
> >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.
>
> --
> 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.

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

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