Patti Use the checkbox under standard control. Then everything should work. Make sure to assign the same component id.
Buddy From: 'Patti Jakusz' via RBASE-L [mailto:[email protected]] Sent: Monday, October 3, 2016 2:22 PM To: [email protected] Subject: Re: [RBASE-L] - Check boxes on reports Hi Buddy, Yes, I did. It tells me it is skipping the "False" line and jumping to the "True" line. But still no checkmark appears in the box. I am watching vGetUHome. I also have the variable displayed on the report, so I know it is what it's supposed to be. I have error set on, but I get no error message. While I don't expect you to review my work, I attached a scaled down version of my database with 1 table and 1 report. Trace pjtest.rmd. Patti _____ From: Buddy Walker <[email protected] <mailto:[email protected]> > To: [email protected] <mailto:[email protected]> Sent: Monday, October 3, 2016 1:06 PM Subject: RE: [RBASE-L] - Check boxes on reports Patti The correct syntax is “CHECKED” Put a trace at the IF block to step through the code and check the value of the “vGetUHome” This way you will be sure which checked is being executed true or false. SET TRACE ON if vGetUHome is null then property CIGetUHome CHECKED 'FALSE' else property CIGetUHome CHECKED 'TRUE' endif SET TRACE OFF Buddy From: 'Patti Jakusz' via RBASE-L [mailto:[email protected]] Sent: Monday, October 3, 2016 12:05 PM To: [email protected] <mailto:[email protected]> Subject: Re: [RBASE-L] - Check boxes on reports I checked the component ID. No spaces. I put the eep back in the "Before Generate detail" section. I traced it and it tells me it's executing the eep line property CIGetUHome CHECKED 'TRUE' right when it's supposed to, but it just doesn't put the checkmark in the box. Is that the correct wording "Checked" ? Patti _____ From: Javier Valencia <[email protected] <mailto:[email protected]> > To: [email protected] <mailto:[email protected]> Sent: Monday, October 3, 2016 11:43 AM Subject: RE: [RBASE-L] - Check boxes on reports Patti, Check your form component and make sure that the component ID “CIGetUHome” does not have a blank at the very end like this “CIGetUHome ”. This used to happen because the paste command used to append a blank space at the end of text copied, I am not sure if it still does. I got caught in this a few times and it is a PIA to find. Now, whenever I assign component ID by copying and pasting, I always check for this. Also, for testing pre-assign a value to vGetUHome just before your command block and then trace the execution and see if and when the command is reached and if it does what is supposed to do. You can repeat the process by pre-assigning NULL value to vGetUHome and repeat the procedure. This approach should pin point where the problem is. Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 From: 'Patti Jakusz' via RBASE-L [mailto:[email protected]] Sent: Monday, October 03, 2016 10:14 AM To: [email protected] <mailto:[email protected]> Subject: Re: [RBASE-L] - Check boxes on reports Yes, the variable is calculated in the detail section, in my variable list. If I do the eep after the detail section, and the checkbox is in the detail section, isn't it too late? Patti _____ From: Buddy Walker <[email protected] <mailto:[email protected]> > To: [email protected] <mailto:[email protected]> Sent: Monday, October 3, 2016 11:07 AM Subject: RE: [RBASE-L] - Check boxes on reports Patti Is your variable being calculated in the detail band. If so and then the eep needs to be in the after detail band Buddy From: 'Patti Jakusz' via RBASE-L [mailto:[email protected]] Sent: Monday, October 3, 2016 11:01 AM To: [email protected] <mailto:[email protected]> Subject: Re: [RBASE-L] - Check boxes on reports Hi Buddy, I was not able to get this to work. Not sure what I did wrong. I put this in the eep that generates before the band. (BTW, I never knew you could do a band-specific eep before.) if vGetUHome is null then property CIGetUHome CHECKED 'FALSE' else property CIGetUHome CHECKED 'TRUE' endif return I placed the variable on the report so I could see if the variable was working right, and it is. Patti _____ From: Buddy Walker <[email protected] <mailto:[email protected]> > To: [email protected] <mailto:[email protected]> Sent: Thursday, September 29, 2016 1:50 PM Subject: RE: [RBASE-L] - Check boxes on reports Patti I’ve used the variable checkboxes in the past and the way I had it working was on the on before generate detail band (assuming you have the check box in the detail band) create the if statements that will check the variable. IF varName IS NULL THEN PROPERTY chkboxComponetID CHECKED ‘FALSE’ ELSE PROPERTY chkboxComponetID CHECKED ‘TRUE’ ENDIF Buddy From: 'Patti Jakusz' via RBASE-L [mailto:[email protected]] Sent: Thursday, September 29, 2016 1:23 PM To: RBASE-L Mailing List <[email protected] <mailto:[email protected]> >; [email protected] <mailto:[email protected]> Subject: [RBASE-L] - Check boxes on reports Hello, I'm using check boxes for the first time on a report in Rbase 9.5 - both Database check boxes and Variable check boxes. I was kind of expecting that if my database column or variable was null, the box would be blank and if it had data in it, there would be a checkmark in my checkbox. But that doesn't seem to be happening - all I get are blank boxes. Exactly what makes the checkmark appear in the box? Thanks, Patti -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
