Interesting... I have to admit I didn't know without looking what mine was set to but I appear to have left it as ON as the default is ON. As I have a start up file that sets all the defaults as I want them then I must have chosen to leave this as the R:Base default but I don't know why I did that.
As far as I am aware I have no problems as it is. Regards, Alastair. ----- Original Message ----- From: [email protected] To: RBASE-L Mailing List Sent: Thursday, January 22, 2009 3:53 PM 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 ------------------------------------------------------------------------------ No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.12/1909 - Release Date: 22/01/2009 07:08
