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]> To: RBASE-L Mailing List <[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]]
