Alastar,

Yes you could.  My point however was that current RBase syntax states when you 
used a variable in a comparison the ones on the left side should NOT be dotted. 
 Currently RBase is very permissive in inforcing this rule.

Thus:
SET VAR LftVar INTEGER = 1
SET VAR RgtVar INTEGER = 0
IF LftVar = .RgtVar THEN  --- PROPER SYNTAX
  .. some commands it var equal
ELSE
  .. some commands if var not equal
ENDIF
 --- Following syntax probably run but RStyle warns that "LftVar" should --- 
not be dotted.
IF .LftVar = .RgtVar THEN 
  .. some commands it var equal
ELSE
  .. some commands if var not equal
ENDIF
Jim Bentley
American Celiac Society
[EMAIL PROTECTED]
tel: 1-504-737-3293


--- On Tue, 6/24/08, Alastair Burr <[EMAIL PROTECTED]> wrote:

> From: Alastair Burr <[EMAIL PROTECTED]>
> Subject: [RBASE-L] - Re: Custom Colors In Reports?
> To: "RBASE-L Mailing List" <[email protected]>
> Date: Tuesday, June 24, 2008, 5:38 PM
> Can you not reverse the logic?
> 
> IF 0 >= .vBF4_OBLIGATED_CHANGE THEN
> 
> Regards,
> Alastair.
> 
> 
> 
> ----- Original Message ----- 
> From: "James Bentley"
> <[EMAIL PROTECTED]>
> To: "RBASE-L Mailing List"
> <[email protected]>
> Sent: Tuesday, June 24, 2008 10:01 PM
> 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
> >
> >
> >
> >
> >
> >
> >
> > -- 
> > No virus found in this incoming message.
> > Checked by AVG.
> > Version: 7.5.524 / Virus Database: 270.4.1/1515 -
> Release Date: 23/06/2008 
> > 19:16
> >
> >


      


Reply via email to