Dan Waters
dwaters at usinternet.com
Sat Apr 7 10:46:44 CDT 2007
Hi Bruce,
----------------------------------------------------------------------------
This is another approach:
COLOR STATUS MEANING
Green New Today (received today)
Unanswered (but hasn't exceeded time limit)
Yellow Over (over response time limit)
Status 4
Orange Status 5
Status 6
Red Status 7
Status 8
You can set up four background colors, and then within the colors you can
use a text field and give a name for the status of that SR. I put in three
examples above.
This could give people the ability to quickly discriminate among the 4
colors, but then know more when they read the Level field. You get an
unlimited number of levels this way, or perhaps 2 levels for green, 4 levels
for yellow, etc.
----------------------------------------------------------------------------
Another approach could be:
COLOR1 COLOR2 (Meaning)
Green White
Green Light Gray
Green Dark Gray
Green Black
Yellow White
Yellow Light Gray
Yellow Dark Gray
Yellow Black
This would give an escalating gray scale within each of the 4 colors. You
get 16 color combinations with this approach.
----------------------------------------------------------------------------
HTH!
Dan
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bruce Bruen
Sent: Saturday, April 07, 2007 8:01 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Reports - Conditional formatting question
On Thursday 29 March 2007 11:05, Darren DICK wrote:
> Hi Bruce
>
> If the background is transparent then you can't apply a colour - well you
> can but it won't be seen
>
> So you need to test for your condition in code then you have to set the
> .background = 1 (Normal) as well and vice versa when turning it off -
> .background =0 if your condition is not met
>
> This is gonna fail in a continuous form by the way a it will apply the
> .background to all field in the continuous list
>
> Haven't tested it but hope this helps
>
> Gimme a yell and I will show you a cool way I handle marking records as
> "current" - or not using conditional formatting
>
>
> See ya
>
> DD
Hi Darren,
I finaly gave up and went with the four available conditional formats (see
my
PEBCAK response. It works, just... but it aint optimal.
I'll pre-empt your offer on the "current" idea as I'm trying to get around 5
or 6 or 7 or ...AAARRRGGHHH... 8 or ... "conditions" on a row, and find a
way
of highlighting the anomalous items. There are about ~7
different "confirmed" anomalies.
1) The service request has not been addressed at all. (conditionalformat
="Highlight")
2) The service request has not been addressed within <timeframe for SR's of
this level> (conditionalformat = "Extreme")
3) The request has been addressed and resolved. (conditionalformat
="Normal")
4) The request has been addressed, but not resolved. (conditionalformat
= "Highlight" - but would like a slightly different colour)
5) The request has been addressed, but not resolved and the resolution
timeframe has expired. (conditionalformat = "Extreme" but should be with an
oxy_torch_flame)
6) The SR has been (manually) escalated - but is still outstanding.
(conditionalformat ="Moderate" + "_zzzzzzzzzzzz" ((SEP)) )
7) The SR response requirement has been over-ridden [conditionalformat =
KILLER! :-( ] ("colour=red,fontsize=172")
8) The SR response requirement has been over-ridden and is overdue
(conditionalformat = "colour=several_thousand_degrees_kelvin_ >_ red,
fontsize=2.326^23, ring bells, flash lights, phone_dad_for_a_lift_home,
light_blue_touch_paper_and_stand_clear")
There may be a couple of gazillion levels between each of the above, I've
only
been able to ascertain this many. "[$DEITY] help me to find the description
if there are any more above (8). :-)
bruce
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com