|
midrange.com
Hmm, kinda makes you want to rewrite all your applications from RPG into CL
and REXX - the freebies, doesn't it? Don't laugh. Back when I worked for
a consultant we had people request PC projects done with Microsoft Basic
because it came with DOS. You can argue with them about programmer
productivity, features and what not but then some chiphead who works for
the client happens to be a whiz with the standard utilities and blows you
away. Frustrating as heck.
Rob Berendt
==================
Remember the Cole!
Alan Addison
<ahaddison@home.c To: RPG400-L@midrange.com
om> cc:
Sent by: Subject: Re: Call Query
owner-rpg400-l@mi
drange.com
10/23/00 03:13 PM
Please respond to
RPG400-L
When you work with a software company that has companies from verrrrry
small to
large as clients, one can not "force" them to do anything they don't want
to.
So one has to deal with what you know will work on all machines.
Alan
rob@dekko.com wrote:
> All the more reason to avoid OPNQRYF. There is no ease of maintenance.
> Instead use SQL. People who stick with OPNQRYF belong to one of few
> categories.
> 1) Work for cheap company which refuses to buy SQL.
> 2) Create vendor software with mandate not to force customers to
purchase
> SQL. (When they've already had to purchase 400, rpg compiler, etc.)
> 3) Have no s*e*x life and last conquest was figuring out OPNQRYF.
> 4) Love to use primary files and can do that if they use OPNQRYF instead
> of SQL.
>
> Rob Berendt
>
> ==================
> Remember the Cole!
>
>
> D.BALE@handleman.
> com To:
RPG400-L@midrange.com
> Sent by: cc:
> owner-rpg400-l@mi Subject: Re: Call Query
> drange.com
>
>
> 10/23/00 10:50 AM
> Please respond to
> RPG400-L
>
>
>
> >But the report does not use the formatting that was
> >set up in Query/400. Is it possible to use that
> >formatting?
>
> Unfortunately, AFAIK, no.
>
> >If not, is there an easy way to make a
> >QMFORM for the QMQRY?
>
> Easy?!?!? No! QMQRY, IMNSHO, is a piece of cr*p as far as being able to
> make
> decent-looking reports. The only way I would not just do all this using
> OPNQRYF / RPG would be if there was already a query out there, and the
> user/boss wanted the absolute quickest & dirtiest way to get it done
*AND*
> understood that the report isn't gonna look all that great.
>
> You gotta look at this from a maintenance perspective, too. Even if you
> are
> able to muddle your way through this, is somebody down the line going to
> have
> to maintain it? Are they going to look at the cryptic source and wonder
> what
> the h*ll possessed you to do this?
>
> If you want a quick way to do nice-looking reports quickly using RPG and
> hate
> using IBM's RLU (Report Layout Utility), get a copy of RDA (Report Design
> Aid)
> - it looks and feels just like SDA and it's a heckuva lot easier to use
> than
> RLU. You'll be cranking out good-looking reports in no time.
>
> Dan Bale
> IT - AS/400
> Handleman Company
> 248-362-4400 Ext. 4952
>
> -------------------------- Original Message --------------------------
>
> > Click the link below
> >
>
http://as400service.rochester.ibm.com/s_dir/slkbase.NSF/$searchform?Open&vie
>
> w=w
> > all
> > In the search field write :
> >
> > Passing Parameters to a Query/400 Query
> >
> > The basic idea of the solution is in the select statement to write in
the
> > Select part:
> >
> > DATE GE :FROMDAT
> >
> > // Yes the : has to be there
> >
> > Save the query as normal i.e. a QRYDFN object.
> >
> > Run the Query with STRQMQRY and ALWQRYDFN(*YES) and set the variables
in
> > SETVAR
> >
> > I.e. in the above case:
> >
> > StrQmQry QmQRy(yourlib/yourqry) AlwQryDfn(*YES)
> > QmForm(*QMQRY) SetVar((FROMDAT 19991122))
>
> This is a great tip! But the report does not use the formatting that was
> set
> up
> in Query/400. Is it possible to use that formatting? If not, is there
an
> easy
> way to make a QMFORM for the QMQRY?
>
> Or is the answer RTFM? ;-)
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
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.
