|
midrange.com
I'll admit it, I'm having a 'day'.
No I understand OPNQRYF and I've used it. Prefer SQL a lot more. Let's
see... OPNQRYF took a couple of manuals to get right, one of them Database
programming. Not to say that SQL doesn't take awhile to grasp also.
Doesn't everyone believe that their code is extremely usable and reliable?
Has it not been said that RPG is self documenting? (I've heard people
quote that from a sales presentation.) I applaud you for your formatting.
I try to do that with my CL and stuff also. However, do you document the
following:
/* Placing the OVRDBF in here to share the open data path with the
OPNQRYF. */
/* Don't try to understand - just know this has to be done */
/* Don't forget to create a work file that has the format you desire */
/* if you use more than one file in OPNQRYF. */
/* Make sure you get the files in the right order and this is why ... */
/* ... go on about matching the format name and so on... */
So yes, I've some experience with OPNQRYF. It's just that SQL makes so
much more sense. I just think that the junior programmer would pickup and
run with the SQL solution better.
And how often do I hear on these lists about people trying to explain how
to substring numerics into OPNQRYF?
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 03:06 PM
Please respond to
RPG400-L
Rob,
So, I'd guess you don't care much for OPNQRYF? <g> What's "All the more
reason to avoid OPNQRYF"? That this is a report request? Or that QMQRY
s*cks? ?????
Never quite learned OPNQRYF? Too bad. Sounds like you've been burned
pretty
bad by it. Just like any other tool, once you know how to use it, it's a
great thing to have in your toolbox. It took me about three weeks to learn
to
use about 80% of it's capabilities.
I have used SQL; it's a great tool. You love it. You never touch OPNQRYF.
Fine. If you've already got SQL, or can make a business case for buying
it,
great. Use the right tool for the job.
But the same can be said for OPNQRYF. Personally speaking, my OPNQRYF code
is
extrememly readable and versatile; I always format the source code so that
QRYSLT tests line up, as well as other parameters'. I do not hesitate to
say
that my OPNQRYF code is very maintainable.
If I can make a business case for buying SQL, I'm sure my company would
spring
for it. Otherwise, your other comments ring hollow with sarcasm.
Why use a diamond-studded gold hammer to drive nails when a standard steel
one
will do? (Unless you're the military. <g>)
<twitch, twitch, as I hesitate to fire this off, triggering another
religious
war - YOU started it, Rob! <g> >
Dan Bale
IT - AS/400
Handleman Company
248-362-4400 Ext. 4952
-------------------------- Original Message --------------------------
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!
>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
+---
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.
