Appreciate that, Jim. I expected somebody to comment on that. You're right. To be honest, I went that direction because I recall Bill_D, or someone, saying that anything inside paren's is treated by the parser as a function. To be honest, I'm not that "tight" on this little-but-potentially serious issue.
My focus yesterday and today was strictly related to report fields being visible||invisible and, if visible, in what color. Still, conceptually, to me, it does seem more intuitive or consistent to use the dotted-var approach for such a comparison, at least when I think about using it for assignment. But it might just be my ignorance and/or incomplete frame of reference. On the color thing, though, like my second message said, cool. Steve -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of James Bentley Sent: Tuesday, June 24, 2008 4:01pm 16:01 To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Custom Colors In Reports? Steve, Just an observation. Even though RBase tightens up does not give an error for the following IF statement "IF (.vBF4_OBLIGATED_CHANGE) <= 0 THEN" Probably because of the paren's and the IF test probably works. If you remove the superfluous parenthesis you get an error of dotted variable on left side of condition. Just one of thos nagging items that someday could come back to haunt if Rbase tightens up its syntax. Jim Bentley American Celiac Society [EMAIL PROTECTED] tel: 1-504-737-3293 --- On Tue, 6/24/08, Wills, Steve <[EMAIL PROTECTED]> wrote: > From: Wills, Steve <[EMAIL PROTECTED]> > Subject: [RBASE-L] - Custom Colors In Reports? > To: "RBASE-L Mailing List" <[email protected]> > Date: Tuesday, June 24, 2008, 1:52 PM > This is a follow-up to yesterday's "Which Approach > to Conditionally & > Dynamically"Create" Control on Report?" > question. > > I have a variable in a report which is assigned a value > from a field/DB > Text, vBF4_OBLIGATED_CHANGE and OBLIGATED_CHANGE, > respectively. If this > value is 0 or less, I want to change the (background) color > of the > control. > > Here is a block in the BEFORE GENERATE EEP: > > IF (.vBF4_OBLIGATED_CHANGE) <= 0 THEN > PROPERTY BF4_OBLIGATED_CHANGE FONT_COLOR 'BLACK' > PROPERTY BF4_OBLIGATED_CHANGE COLOR 'YELLOW' > ELSE > PROPERTY BF4_OBLIGATED_CHANGE FONT_COLOR 'BLACK' > PROPERTY BF4_OBLIGATED_CHANGE COLOR 'WHITE' > ENDIF > > > This works. > > However, this statement does not : > > PROPERTY BF4_OBLIGATED_CHANGE COLOR 'CYAN' > > > Nor does : > > PROPERTY BF4_OBLIGATED_CHANGE COLOR 'LIGHT CYAN' > > > (Interestingly, each and every failed attempt changed the > background to > green.) > > > Also interesting, these statements do work : > > PROPERTY BF4_OBLIGATED_CHANGE COLOR > 'ActiveCaption' > > PROPERTY BF4_OBLIGATED_CHANGE COLOR 'AQUA' > > > So, my questions are: > 1) Which colors are available for changing the background > of a DB Text > in Reports? > 2) Where are their "names" found/stored? > 3) Can I add new colors or redefine existing, in either > case using R,G,B > values? > > > > Thanks, > Steve in Memphis > > > > > J. Stephen Wills > Program Manager, Research Informatics > Office of the Vice Chancellor for Research > University of Tennessee Health Science Center > 62 S. Dunlap, Suite 400 > Memphis, TN 38163 > Office: 901-448-2389 > FAX : 901-448-7133
