At 08:44 AM 9/7/01 -0400, J.M. GRATIAS wrote:
>I went there yesterday and could look at the problem because it
>happen regularly : on some forms, probability is 25% (4 loops
>and he is pretty sure to be exited for RBW).
>I installed RBW 6.5++ : no change.
J.M.,
Obviously, the problem is with your application or coding method.
01. How many RUN statements you have in your WHILE loop?
02. What is the default setting for FILES?
SHOW FILES
02. Are you changing the data type within a WHILE loop?
03. Are you CLEARing any required variable(s) within WHILE loop?
04. Have you tried using the cool technique of using QUIT TO
instead of RUN? (my preferred technique ...)
>I could't make it hang in TRACE mode, but it seems that problem
>on ENTER line.
That's blue's clues ...
That is a very clear indication that you have a few variables with
different data types OR the required variable(s) are NOT pre-defined.
FYI, the TRACE command does NOT use the optimizes method (WHILEOPT OFF)
to TRACE/DEBUG. In other words, WHILEOPT is SET to OFF when using the
TRACE/DEBUG command.
The WHILEOPT setting is used to optimize WHILE loops in a command file.
The default is set to ON.
Easy steps to resolve such issues (General Rules):
01. IF the data entry form includes any variables, THEN, make sure
that ALL variables are defined prior to using ENTER USING command
02. Make sure that the Data Type of ALL pre-defined variable(s) match
with the Variable Objects in Form.
03. Check ALL EEPs (if any) to make sure that the data type of any
variable(s) is NOT changed.
04. While TRACing/DEBUGging your application code, make sure to use
F10 key (Single Step Method).
05. While TRACing/DEBUGing your application code, make sure to use
F6 key (Add Watch Variables).
06. Pay attention to those watch variable(s), as defined above, for
any change in data type.
07. Does your EEPs or RUN procedures include the RETURN command at
the end of any procedure to get back to the originating command
or located column/variable in form.
08. Last but not least, you might want to use SET WHILEOPT OFF at the
beginning of your command file or just before using the WHILE
command and see what happens. Make sure to set back to ON after
the ENDWHILE statement for improved performance.
Good Luck!
Very Best Regards,
Razzak.
===================================-============================
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.
==================================-=============================
