Patti, I was off line for a while and just got back on. For CASE 1 and 2 you would have the same PROPERTY code since you want it to go to the same field. You could add a focus code as well if you wanted to so the cursor would go to the DBedit field. PROPERTY <componentID> SET_FOCUS ‘TRUE’ It is not necessary. It depends on how automated you want to get.
The great thing about using the PROPERTY command is you can show just what you want. In my code for one of my forms, only the first radio group shows. Once a choice is made, then only the next radio group shows based on the choice in the first radio group. This continues until, on this form, a report is ready to generate. It does not have to be this way. Some forms have all radio groups showing and the code eliminates items no chosen. It really comes down to what your people want to do and the ease of understanding the form. James Belisle Making Information Systems People Friendly Since 1990 [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of Patti Jakusz Sent: Monday, January 19, 2015 6:28 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Need a skip pattern suggestion So, for example, I have a form named BiiAdd and a field named Outcome. If Outcome = 1, 2 or 3, I want it to go to Outdate (a DBedit field) If Outcome = 4, I want it to go to Cribcard (a DBRadio group) So I'm thinking this is what my Exit EEP will be for field Outcome Switch (Outcome) Case 1 Case 2 Case 3 property BiiAdd_Outdate visible 'True' break Case 4 property BiiAdd_Outdate visible 'False' property BiiAdd_Cribcard visible 'True' property BiiAdd_Cribcard radiobuttons visible 'True' break Endsw Is this correct? Thanks, Patti ________________________________ From: Jim Belisle <[email protected]<mailto:[email protected]>> To: RBASE-L Mailing List <[email protected]<mailto:[email protected]>> Sent: Monday, January 19, 2015 4:06 PM Subject: [RBASE-L] - RE: Need a skip pattern suggestion Patti, I use radio groups all the time and you can control which radio buttons come up using the PROPERTY commands. It is not that difficult since I learned it. You can also include the SWITCH command with the CASE command. Below is an example. SWITCH (.vreportuse) CASE 'Distinfo' PROPERTY comp_reset VISIBLE 'TRUE' PROPERTY comp_custtype VISIBLE 'TRUE' PROPERTY comp_custtype radiobuttons[4]->VISIBLE 'FALSE' PROPERTY comp_custtype radiobuttons[5]->VISIBLE 'FALSE' BREAK CASE 'QuickOpen' -- Added this option on 5/18/2012 PROPERTY comp_reset VISIBLE 'TRUE' PROPERTY comp_custall VISIBLE 'TRUE' SET VAR vcusttype = 'DIST' SET VAR vctchoice = '(DIST,RES,DIR)' BREAK ENDSW 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: Monday, January 19, 2015 2:05 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Need a skip pattern suggestion I have a form with lots and lots of DB Radio Groups. There are lots of skip patterns to follow, based on the answers to previous questions. Since you can't really use the "skip to" command in an eep for DB radio groups, I was thinking of placing a little DBedit field in front of each question that can be highlighted. If a previous question is answered in one way, I could skip to the little field in front of the question that should be next. I could have to "in focus" color be something bright. Is there a better control to use than DBedit? Is there an easier way to do it? I don't know how to use Get Property. (I learned Get Property in 2008 but didn't use it fast enough and I forgot it. Next time I go to a class, I'm going to record it.) Thanks, Patti
