Hi Razzak, I understand that issue.
My observation was that when code executes DIFFERENTLY in TRACE mode, it can make debbugging a lot harder. Dennis McGrath -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of A. Razzak Memon Sent: Wednesday, January 25, 2006 5:16 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Error At 05:59 PM 1/25/2006, Dennis McGrath wrote: > >>If I trace it NO ERROR run it and ERRORS > >This seems to be a legacy "bug???" > >I often see situations where an expression works great in trace but >errors in standard run. > >I've seen this several times in the last week on 6.5++ DOS I'm scrating >my head about how an expression could fail except when I trace. It does >make for some creative debugging work. Dennis, If you pre-define all variables accordingly with CORRECT data types, you'll never have to scratch your head again. <g> And that is exactly how Victor Timmons took care of his -ERROR-. As mentioned in my earlier post, TRACE runs with WHILEOPT OFF. The default is set to ON. SET WHILEOPT improves the optimization and processing of WHILE ...ENDWHILE loops within applications by pre-compiling variables used within the WHILE loop. Very Best R:egards, Razzak.
