Ok, I have it reproducible. The issue seems to be with "RNF7503:
Expression contains an operand that is not defined" when that error is
due to a field not defined. If I double-click that error, it shows up
in my source. However, once I click on the source, they disappear
(because to the in-line syntax checker, it doesn't know that a field
isn't defined, and it looks ok).
Kurt Anderson
Application Developer
Highsmith Inc
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Justin Taylor
Sent: Monday, August 27, 2007 9:05 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Another issue after going to WDSCi 7.0 - Verify
I do not use the Automatic syntax checking due to issue with SQLRPGLE
source members, so I have never seen this problem.
My first suggestion would be to disable the syntax checking and see what
happens. If that is undesirable, try clearing your cache and setting
WDSc to not include informational messages.
--
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.
As an Amazon Associate we earn from qualifying purchases.