Alastair: Not sure if you meant me and what I posted. My posting is a very simple example, where you just want a word to appear in a certain color if a condition exists. This works in a region. You just define your form variable as I show below in the IFEQ, having a blank as the result if you want nothing to appear. You locate the form variable as a label in your region, and assign the color red. This does NOT address having the variable change colors depending on a condition or not. I suppose you could have 2 variables, with 2 different colors, if you could work that into your display so that it makes sense.
Karen > Sami, > > Would you mind explaining briefly, please, how you do that? > > I have a form where I try to highlight rows where some item in the row has > incomplete data but I have never been able to get it to really look right. My > method works but it's not as effective as I'd like. I already use a variable > label but my quick attempt to use an On Row Entry EEP just now to change the > colour didn't work so I guess that I'm just going about it the wrong way. > > Thanks ®ards, > Alastair. > > > > >> ----- Original Message ----- >> From: [EMAIL PROTECTED] >> To: RBASE-L Mailing List >> Sent: Tuesday, July 15, 2008 3:09 PM >> Subject: [RBASE-L] - Re: Colored object in Scrolling Region >> >> >> Sami: I assume you want to change a DBEdit field? If so, then I agree >> with Larry. But Labels will evaluate fine per row. I do that all the time. >> >> If it's an editable field, anyway you can get around with putting words >> around the field in a color? Like maybe defining a form expression: >> vAsterisks = (IFGT( columnname, 0, ' ', '****')) >> and make the field red? >> >> Karen >> >> >> >>> Sami -- I believe you're out of luck. In scrolling regions, and even >>> in the underlying Windows construct, an item repeated in each band will >>> have >>> the same properties. >>> >>> If the object in question is text, can you fake it out by having two >>> different objects calculated in the variables list, with the (say) red one >>> evaluating to NULL when it should display b >> >
