Re: Best Practice - Compiling SQLRPGLE w/Errors

Thanks Peter...that's a better approach than what I was doing.

On 11/10/06, Peter.Colpaert@xxxxxxxxx <Peter.Colpaert@xxxxxxxxx> wrote:

What I do is re-open the original source member and let the verifyer do
what it's there for.

Just my .02 euro

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----



"Michael Ryan" <michaelrtr@xxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
10/11/2006 14:17
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] Best Practice - Compiling SQLRPGLE w/Errors






What's the best practice for fixing SQLRPGLE compile errors in WDSc?
AFAIK,
the problem of double clicking the compile error and WDSc bringing up an
RPGLE member still exists. What's the best way to deal with this? Just
deal
with it? :) Use a combination of green screen compiles and WDSc editing?
--
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.

--
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.