Thank you, Doug.  I may try this.
Patti
      From: Doug Hamilton <[email protected]>
 To: RBASE-L Mailing List <[email protected]> 
 Sent: Friday, January 23, 2015 12:57 PM
 Subject: [RBASE-L] - RE: Embedded eep on a variable edit field
   
  Good idea, Javier.  I also place a SET TRACE OFF before each RETURN.
 And, to make it easier, I place a small (30x30) transparent enhanced speed 
button (ComponentID = CIDDeBugButton) on forms that allows me to toggle DEBUG 
on and off; it is password protected.
 
 The On-Click EEP is a RUN SELECT so it can used on any form:
 --Debug EEP for all forms
 SET VAR vDeBugPW TEXT
 IF vDeBugPW <> 'whatever' OR vDeBugPW IS NULL THEN
   DIALOG 'Enter password or click Cancel to continue.' +
    vDeBugPW=8 vEndKey  PASSWORD +
    CAPTION 'Start Debug' ICON Stop
 ENDIF
 
 IF vDeBugPW = 'whatever' THEN
   IF (CVAL('DEBUG')) = 'On' THEN
     SET DEBUG OFF
     PROPERTY CIDDeBugButton CAPTION ' '
   ELSE
     SET DEBUG ON
     PROPERTY CIDDeBugButton CAPTION 'Debug On'
   ENDIF
 ELSE
   CLEAR VAR vDeBugPW
 ENDIF
 
 RETURN
 
 For added security, I suppose you could clear vDeBugPW before RETURN, but then 
you'd have to re-enter it to turn debug off.
 Doug
 
 On 1/23/2015 10:58 AM, Javier Valencia wrote:
  
 <!--#yiv2974123412 _filtered #yiv2974123412 {font-family:Helvetica;panose-1:2 
11 6 4 2 2 2 2 2 4;} _filtered #yiv2974123412 {font-family:Helvetica;panose-1:2 
11 6 4 2 2 2 2 2 4;} _filtered #yiv2974123412 {font-family:Calibri;panose-1:2 
15 5 2 2 2 4 3 2 4;} _filtered #yiv2974123412 {font-family:Tahoma;panose-1:2 11 
6 4 3 5 4 4 2 4;}#yiv2974123412 #yiv2974123412 p.yiv2974123412MsoNormal, 
#yiv2974123412 li.yiv2974123412MsoNormal, #yiv2974123412 
div.yiv2974123412MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New 
Roman", "serif";}#yiv2974123412 a:link, #yiv2974123412 
span.yiv2974123412MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv2974123412 a:visited, #yiv2974123412 
span.yiv2974123412MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv2974123412 
p.yiv2974123412MsoAcetate, #yiv2974123412 li.yiv2974123412MsoAcetate, 
#yiv2974123412 div.yiv2974123412MsoAcetate 
{margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"Tahoma", 
"sans-serif";}#yiv2974123412 span.yiv2974123412EmailStyle17 
{font-family:"Calibri", "sans-serif";color:#1F497D;}#yiv2974123412 
span.yiv2974123412BalloonTextChar {font-family:"Tahoma", 
"sans-serif";}#yiv2974123412 span.yiv2974123412SpellE {}#yiv2974123412 
.yiv2974123412MsoChpDefault {font-size:10.0pt;} _filtered #yiv2974123412 
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv2974123412 div.yiv2974123412WordSection1 
{}-->  Patti, There is no need to guess where the problem is. We have a 
wonderful tool in TRACE that allows you to execute your code one line at the 
time and you  can find exactly where your problem is. Every code I write I 
place the following command at the top: DEBUG SET TRACE ON When I need to debug 
code, at the R> prompt I enter the command: SET DEBUG ON And when I run my code 
it goes automatically into the debug mode. When I am done debugging I simply: 
SET DEBUG OFF and the code runs normally. It is a great tool to figure out if 
your code is running as designed and in the correct sequence, and when you run 
into  an error/warning, it will display it for you so you can correct it 
accordingly. You can also display variable and it will show changes in real 
time.     Javier,    Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 
913-915-3137       From: [email protected] [mailto:[email protected]] On Behalf 
Of Patti Jakusz
 Sent: Thursday, January 22, 2015 10:54 PM
 To: RBASE-L Mailing List
 Subject: [RBASE-L] - RE: Embedded eep on a variable edit field        Yes, 
they were set up ahead of time.  I think the "Skip to" commands were causing 
the problem.          Thank you though.   Patti          From: Buddy Walker 
<[email protected]>
 To: RBASE-L Mailing List <[email protected]> 
 Sent: Thursday, January 22, 2015 5:32 PM
 Subject: [RBASE-L] - RE: Embedded eep on a variable edit field   
 Are all variables set before entering form, if so are they being cleared once 
form executes
 
 -----Original Message-----
 From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle
 Sent: Thursday, January 22, 2015 4:44 PM
 To: RBASE-L Mailing List
 Subject: [RBASE-L] - RE: Embedded eep on a variable edit field
 
 Using the rstyle to see where the error is, should help you figure where you 
are breaking the code.
 Also changing to the PROPERTY command as Karen suggested is nice.
 
 James Belisle
 
 Making Information Systems People Friendly Since 1990 
[cid:[email protected]]
 
 From: [email protected] [mailto:[email protected]] On Behalf Of Patti Jakusz
 Sent: Thursday, January 22, 2015 3:42 PM
 To: RBASE-L Mailing List
 Subject: [RBASE-L] - RE: Embedded eep on a variable edit field
 
 Hi Jim,
 No, there's no Switch or Case.  I just used an If statement because I'm 
testing for anything below 12 or ge 12.
 
 Patti
 
 ________________________________
 From: Jim Belisle <[email protected]<mailto:[email protected]>>
 To: RBASE-L Mailing List <[email protected]<mailto:[email protected]>>
 Sent: Thursday, January 22, 2015 3:55 PM
 Subject: [RBASE-L] - RE: Embedded eep on a variable edit field
 
 Is this EEP located in a SWITCH or CASE part of your code?
 
 James Belisle
 
 Making Information Systems People Friendly Since 1990 
[cid:[email protected]<mailto:[email protected]>]
 
 From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] On Behalf Of Patti Jakusz
 Sent: Thursday, January 22, 2015 2:37 PM
 To: RBASE-L Mailing List
 Subject: [RBASE-L] - Embedded eep on a variable edit field
 
 I'm trying the embedded eeps in an object instead of calling an external eep, 
for pretty much the first time.
 
 I have a variable edit field.  It's the 3rd field on the form, but since the 
other two are radio groups, it skips over those and goes right to the variable  
edit field.  I "get" why it does that.
 
 But I get an error message when I try to leave the variable edit field, and 
again eveytime the cursor lands on it.  (happens a lot when I'm testing other 
things.)
 
 Here's my eep, that is executed upon leaving the field:
 
 if vine01ed < 12 then
     property BiiAdd_INE01GED visible 'true'
     property BiiAdd_e1a visible 'true'
     skip to INE01GED
 else
     property BiiAdd_INE01GED visible 'false'
     property BiiAdd_e1a visible 'false'
     skip to vine04ed
 endif
 return
 
 The error messages I keep getting are:
 -ERROR- No WHILE, SWITCH or IF blocks are open on current input source. ( 466) 
Switching input back to keyboard
 
 It actually makes the other fields appear or disappear ok.  But why the error?
 
 Thanks,
 Patti
 
 
       
 
 


|      |   This email has been checked for viruses by Avast antivirus software. 
www.avast.com   |




  

Reply via email to