I am learning here about the trace. I, like Patti, used trace only at the R prompt or I would run the command file with trace on if I was testing command files prior to implementing. So are you saying, Javier, that you use the code DEBUG SET TRACE ON while the application program is running? Or are you just talking about prior to implementation in an application?
James Belisle Making Information Systems People Friendly Since 1990 [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of Patti Jakusz Sent: Friday, January 23, 2015 3:09 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: TRACE Thank you, Bruce. I thought 'set Echo on' would do the same, but sometimes it isn't specific enough. Patti ________________________________ From: Bruce A. Chitiea <[email protected]<mailto:[email protected]>> To: RBASE-L Mailing List <[email protected]<mailto:[email protected]>> Sent: Friday, January 23, 2015 12:38 PM Subject: [RBASE-L] - TRACE Patti: As a relative beginner whose heinie is rescued daily by TRACE, I enthusiastically second Javier’s (well written) suggestion to you. The initial time spent learning TRACE, applied in precisely the manner he suggests, pays dividends in orders of magnitude. As an aside – anyone? - a focused on-line TRACE class would be one amazing add for R:Base programmers. Best of luck, Bruce Chitiea SafeSectors, Inc. eCondoMetrics 909.238.9012 cell From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Javier Valencia Sent: Friday, January 23, 2015 8:58 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Embedded eep on a variable edit field 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]> [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]<mailto:[email protected]>> To: RBASE-L Mailing List <[email protected]<mailto:[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]> [mailto:[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]<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 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]><mailto:[email protected]<mailto:[email protected]>>> To: RBASE-L Mailing List <[email protected]<mailto:[email protected]><mailto:[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]><mailto:[email protected]<mailto:[email protected]>>] From: [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> [mailto:[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
