Karen, I standardize on WHILEOPT OFF for the exact reasons you outline.
There are only about 4 places in my huge app that I set it on. The problem with WHILEOPT is the "RULES" make for code that is difficult to maintain. If you make changes to a while loop, you risk breaking your code in so many entertaining ways. The fact that TRACE intrinsically turns WHILEOPT OFF exacerbates the problem, because your code now works differently in trace that it does otherwise. Dennis McGrath ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, January 22, 2009 9:54 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Typecasting problem Jason: I'd be tempted to set whileopt off in your startup program and leave it there. The funny thing about having whileopt ON is that it doesn't always create problems in the exact place where it IS a problem. The memory problems just keep accumulating and eventually your app bombs out somewhere else with no connection to the actual problem. We don't take "surveys" on this list, but if we did, I'll bet that over 90% of programmers set whileopt off for their entire app. It was introduced way back in some DOS version when code speed was a huge issue. Whileopt ON made the code run faster (supposedly) but along with it came some stringent coding "rules" that you had to follow or else you ran into these memory issues. So rather than asking programmers here who sets it on or off, I'd like to hear from programmers who purposely set whileopt ON for the entire app, have no problems with it, and have done it for a particular reason. Karen Razzak and Karen, Thank you. Setting WHILEOPT to OFF for just that loop fixed it. Jason
