Razzak & Dennis,
One of the problems I often encountered was problems with WHILE loops. In the past there was a limit on the number of objects/statements which could be contained in an optimized WHILE loop. Also in there were restrictions on things you could do with defining and changing and deleting variables used in the loop. For optimization to work you need to predefine variables outside the loop. Not change variable type within the loop. YOu must not clear nor redefine a variable within the loop. If you need to clear within the loop Set the variable to NULL.
Follow these rules eliminate most problems.
Some times it is difficult to spot the problems. Many years ago Microrim distributed a program which created a formatted list of CMD/RMD/APP files It printed a line number, indicated nesting levels and produced a variable cross referenced list. I belive that if it was processing an APP file it also procuced a list of COMMAND/MENU/SCREEN blocks. I sem to remember that this program existed for version before names could be up 18 characters.
Of course this was before RSTYLE was developed. Perhaps some day RSTYLE could be enhanced to produce a report that indicates nesting levels and procuduces a useable Cross Reference.
Jim Bentley
American Celiac Society
"A. Razzak Memon" <[EMAIL PROTECTED]> wrote:
One of the problems I often encountered was problems with WHILE loops. In the past there was a limit on the number of objects/statements which could be contained in an optimized WHILE loop. Also in there were restrictions on things you could do with defining and changing and deleting variables used in the loop. For optimization to work you need to predefine variables outside the loop. Not change variable type within the loop. YOu must not clear nor redefine a variable within the loop. If you need to clear within the loop Set the variable to NULL.
Follow these rules eliminate most problems.
Some times it is difficult to spot the problems. Many years ago Microrim distributed a program which created a formatted list of CMD/RMD/APP files It printed a line number, indicated nesting levels and produced a variable cross referenced list. I belive that if it was processing an APP file it also procuced a list of COMMAND/MENU/SCREEN blocks. I sem to remember that this program existed for version before names could be up 18 characters.
Of course this was before RSTYLE was developed. Perhaps some day RSTYLE could be enhanced to produce a report that indicates nesting levels and procuduces a useable Cross Reference.
Jim Bentley
American Celiac Society
"A. Razzak Memon" <[EMAIL PROTECTED]> wrote:
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.
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.
Jim Bentley
American Celiac Society
[EMAIL PROTECTED]
tel: 1-504-737-3293
Bring words and photos together (easily) with
PhotoMail - it's free and works with Yahoo! Mail.
