Nope, I never bother turning it ON. Not once... That setting was really important back in DOS and slow-computer days when we were trying to steal every ounce of processing power. Of course I still want stuff to go fast, but I honestly have had no complaints about RBase's speed. If I ever wanted to turn it "on" to optimize a while loop, I would have to go back and read the "rules" to make sure I get it right. I make it a rule (haha) to still incorporate some of those guidelines into my coding, whileopt or not, like I never initialize a variable with datatype within a while loop, such as: set var vtext text = 'hello'.
Remember, it only optimizes a while loop if you adhere to the programming rules. If you don't follow all the rules, then your while loops will leak and the issue comes up eventually somewhere else in your code. Karen -----Original Message----- From: Jim Belisle <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Wed, Apr 15, 2015 10:08 am Subject: [RBASE-L] - Re: Main application closing Since the WHILEOPT is used to optimize the WHILE loops, would you then turn it on and off when you want to take advantage of this option? Since it is a default of ON I have never played with this setting. James Belisle Making Information Systems People Friendly Since 1990 [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of Karen Tellef Sent: Wednesday, April 15, 2015 10:01 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Main application closing Do you run with WHILEOPT ON? That's usually my first question for stuff like this. If you run with it on and you break one of the coding "rules" for whileopt, then you start piling up memory without releasing and somewhere down the line everything shuts down. I always run with it off. Karen -----Original Message----- From: Jim Belisle <[email protected]<mailto:[email protected]>> To: RBASE-L Mailing List <[email protected]<mailto:[email protected]>> Sent: Wed, Apr 15, 2015 8:54 am Subject: [RBASE-L] - Main application closing One part of the application we use in the office, is for order entry. This is a compiled application used throughout the company. The forms and reports reside within the DB. My order entry person mentioned an inconsistent problem to me yesterday. When entering orders in the order entry form, she can enter new customers using another form. Once the new customer is entered and the customer entry form is closed, the ID is then available to use in the ID field. She states that SOMETIMES after entering a new customer, when she goes to type in the new ID in the proper order entry field, the whole RBASE application closes. As I said, this happens just sometimes. At other times, everything works as it should. The button bringing up the customer entry form is simple enough. SET VAR vFormMode = 'Enter' ENTER USING KayParkDistInfo FOR 1 ROW PROPERTY DBComboBox_Distributor REFRESHLIST TRUE CLEAR VAR vFormMode RETURN Once the new ID is entered, the field on the order entry form is a DB Lookup Combo Box. Anyone have an blues clues? James Belisle Making Information Systems People Friendly Since 1990 [cid:[email protected]<mailto:[email protected]>]
