At 12:08 AM 2/14/2002 -0500, Mike Sinclair wrote:
>Is there a list of reasons why an error might not >show up using Trace, but would show up using Run? >It can be very frustrating when that happens! TRACE does not use the WHILE loop optimization or SET WHILEOPT OFF. That will turn off WHILE loop optimization. If you determine that the problem is with an optimized command, review the rules above, you may be clearing, retyping or not correctly data typing a variable. Most common causes: . Mismatched variable(s) . Variable(s) with WRONG data types Very Best Regards, Razzak. ===================================-============================ R:BASE Developers's Conference: http://www.rbase.com/conference Official R:BASE List Server: mailto:[EMAIL PROTECTED] RBTI Events/Training: http://www.rbase2000.com/events R:DCC Members: http://www.rbase2000.com/rdcc ================================================================ R:BASE, Oterro & R:Tango are registered trademarks of RBTI. ==================================-============================= ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
