Thanks Dawn,

Setting whileopt off makes no difference but it does seem to have something to 
do with the while loop.  If I remove the loop, the problem goes away.  All the 
variables seem to be defined but I will take a closer look at them.

Thanks again,
Michael


Michael Moser
EXAQ Micro Services
www.exaq.com
Phone: 916-966-8313
Fax: 916-966-8313

 >>  If I recall, it usually means there's a problem within the  while loop. 
 >>  Set whileopt off to see if there's a difference.  If  Trace runs fine
 >>  with whileopt off, make sure all variables needed in the  while loop are
 >>  declared before the while statement.  
 >>  You'll probably find  during your conversion that there are quite a few
 >>  instances where you did things  not exactly right in 6.5, but it worked -
 >>  now it won't. 7.1 is much more  stringent about proper coding.   Dawn 
 >>  From: Michael Moser  
 >>  [mailto:[EMAIL PROTECTED] 
 >>  Sent: Thursday, March 17, 2005 12:22  PM
 >>  To: RBASE-L Mailing List
 >>  Subject: [RBASE-L] - Conversion  issues - eeps go wacky with TRACE

 >>  Hi All,  I tried to send this to the RB7 server but it does not seem to be
 >>  going  through so I thought I would see if any of you converting 6.5 to
 >>  7.1 might have  a thought.
 >>  I have run into a problem with forms containing EEPs that worked  fine in
 >>  6.5++  but act strangely when run with TRACE in 7.1.  I have short eep
 >>  that assigns a variable when leaving a button.  The  button has a custom
 >>  eep:   FVar.eep using 'X', 'Prn1'
 >>  The FVar.eep contains:   SET V FormVar TEXT = .%2 
 >>  IF %1 = 'X'  THEN   
 >>  CLOSEWINDOW 
 >>  ELSE 
 >>  ENDIF  RETURN  FormVar is processed by a SWITCH statement after the form
 >>  closes.  It  seems to work fine when run normally, but here is the
 >>  strange behavior when run  from TRACE.  - When the button is clicked,
 >>  TRACE shows the first line in the EEP as  
 >>  expected. - Pressing F10 takes the highlight straight to the RETURN line, 
 >>  unexpectedly skipping all the lines in between. - Pressing F10 returns to
 >>  the form. - Clicking the button a second time again shows the Highlight
 >>  on the  first line in the TRACE 
 >>  screen. - This time pressing F10 processes each line correctly as
 >>  expected. - After the RETURN is processed, the form closes and the
 >>  calling module  unexpectedly processes as if the F5 key had been pressed
 >>  or TRACE is  no longer functioning.  The form is 
 >>  called from a simple while loop with: ...    EDIT USING AskQuestion WHERE
 >>  FSId = 1
 >>  ...  This behavior makes it difficult to troubleshoot any problems after
 >>  the  form as TRACE is no longer providing step by step functionality. 
 >>  Anyone else encounter a problem like this.  Thanks, Michael  
 >>  Michael Moser
 >>  EXAQ Micro Services
 >>  www.exaq.com
 >>  Phone:  916-966-8313
 >>  Fax: 916-966-8313

--- RBASE-L
=======================3D=======================3
D=
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]

(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
=======================3D=======================3
D=
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
=======================3D=======================3
D=
TO UNSUBSCRIBE:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
=======================3D=======================3
D=
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body,
place any
text to search for.
=======================3D=======================3
D=

Reply via email to