WDSC Parser Stuck in RPGLE

Here's another one...I had to change the attribute of an RPGLE program to SQLRPGLE. Having done that, I would expect WDSC to pick up on the change, but it doesn't. It does show the correct attribute under the Remote Systems tab, but in the LPEX editor it continues to show the member as RPGLE and parses it as such.

I go to change this under Windows, Preferences, LPEX Editor, and expand the branch of the source member and select Parser. It continues to show ILErpg as the parser, so I switch it to ILErpgSql. While I have the current member open it correctly parses it (e.g. you see the correct color coding on the EXEC SQL statements). The tab still shows RPGLE. No matter what I do (close it and reopen, close WDSC and restart it), it still thinks the source is RPGLE and uses that parser the next time I open it.

I have done several different refresh options (related to my earlier issue with Verify) but nothing seems to affect it. Anyone with suggestions or a solution to get this to use the correct parser?

Side note: I have a coworker who showed me a feature in Aldon that compiles the source and provides a listing of errors, much like the Verify command. I'm still curious as to what would have caused the Verify command to suddenly stop working, even though I had the library in the library list where the files resided. However I do have a workaround to address this with the Aldon feature...so if anyone has some spare time (heh) or is up to a challenge on a small annoyance, go for it. Thanks.

Ken Tarr
Associated Banc Corp
Green Bay Service Center, Mail Stop 7055
2870 Holmgren Way
Green Bay, WI 54304
www.associatedbank.com



*********************** NOTICE***********************

This e-mail and attachment(s) may contain information that is
privileged, confidential, and/or exempt from disclosure under
applicable law. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination,
distribution, or copy of this message is strictly prohibited. If
received in error, please notify the sender immediately and
delete/destroy the message and any copies thereof. Although
Associated Banc-Corp and/or its affiliates (collectively
"Associated") attempt to prevent the passage of viruses via e-mail
and attachments thereto, Associated does not guarantee that either
are virus-free, and accepts no liability for any damage sustained
as a result of any such viruses.

Any federal tax advice contained in this communication (including
any attachments) is not intended or written to be used or referred
to in the promoting, marketing, or recommending of any entity,
investment plan or agreement, nor is such advice intended or written
to be used, and cannot be used, by a taxpayer for the purpose of
avoiding penalties under the Internal Revenue Tax Code