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