Re: Must I use OPNQRYF

I'm comfortable with OPNQRYF and getting more comfortable with SQL as time
goes on. SQL is more flexible and I have done things with embedded SQL
that I simply could not have done with OPNQRYF.

That being said, do you know what I miss the most when I use an embedded
SQL cursor instead of OPNQRYF for reports? Don't laugh, but it's the
control (level) breaks built into RPG for report programs. They make it so
clean and simple for report programs. And no, I am not at all interested
in regurgitating the 'cycle' debate.



On Mon, Feb 20, 2012 at 10:12 AM, Mike Wills <mike@xxxxxxxxxxxx> wrote:

I never had good luck with OPNQRYF. I switched to SQL and never looked
back.

--
Mike Wills
http://mikewills.me

Sent from my mobile phone

On Feb 20, 2012, at 8:56 AM, sjl <sjl_abc@xxxxxxxxxxx> wrote:

Mike -

CPYFRMQRYF ?

;-)

- sjl


Mike wrote:
That is why I use SQL.

OPNQRYF was a PITA. At least with SQL I can

test the data easily in STRSQL or your favorite SQL client. <<<

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