Thanks Albert. Modifying the logic so that no errors would ever be generated is doable. What I'm trying to determine is if it's necessary for stability. Another example would be setting off 2059 (no rows satisfy the where clause) prior to executing a command that might return no rows as opposed to preceding the command with an additional select count(*) in order to not risk generating the 2059 error.
Is the rule of thumb "don't ever cause an error to be generated" or can we allow them, suppress them from the interface and utilize the performance advantage? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Albert Berry Sent: Friday, August 20, 2010 2:32 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: ERROR 235 - Insufficient space to process command If you suspect more than one row might appear, don't turn the error off, use LIMIT instead. SELECT CustCity from Customers where CustID = 123 and LIMIT = 1 This will return only the first row found, which is what would happen anyway, but will generate no error messages Albert Steve Martin wrote: > > Out of curiosity, I wonder if the generation of any error condition > could lead to problems like this. For example, I would not consider it > dangerous to select a value from a table into a variable knowing that > there might be multiple rows that satisfy the where clause. In fact, > sometimes it's expected and okay so I'll just set error message 2441 > off prior to the select statement and turn it back on after. Is it > possible that this practice would cause the memory environment to > become unstable or, if the error message is a misrepresentation, to > cause subsequent insert/update commands to fail? How about if I don't > use an indicator variable and suppress those messages? > > Would really like to stabilize this system and any suggestions would > be appreciated. > > ------------------------------------------------------------------------ > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of > *Steve Vellella > *Sent:* Tuesday, August 17, 2010 10:17 AM > *To:* RBASE-L Mailing List > *Subject:* [RBASE-L] - RE: ERROR 235 - Insufficient space to process > command > > Steve, > > That error can be caused by invalid expressions (typically with > unbalanced parenthesis or unbalanced quotes). > > That would be the first thing I would look for. > > Steve > > Steve Vellella > > Office: 520-498-2256 > > Cell: 520-250-6498 > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of > *Steve Martin > *Sent:* Tuesday, August 17, 2010 9:59 AM > *To:* RBASE-L Mailing List > *Subject:* [RBASE-L] - ERROR 235 - Insufficient space to process command > > Hey group, > > Anyone have insight into what might cause (apparently) sporadic > occurrences of error 235 - ERROR - Insufficient space to process _____ > command? We're seeing these be generated from various procedures on > various computers; not frequent, but frequently enough to grow weary > of correcting incomplete transactions. > > To better understand what space we're talking about and how better to > manage it would be helpful. > > Thanks, > > Steve > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.851 / Virus Database: 271.1.1/3051 - Release Date: > 08/15/10 23:35:00 > No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.851 / Virus Database: 271.1.1/3051 - Release Date: 08/15/10 23:35:00
