Ah, well... picking up that line of thought, I tested my values a little more thoroughly and found that the conditions DID evaluate properly *as long as none of the values were BLANK.* There had to be a number in each field, even if that number was 0.

Which now begs the question: What would be the most appropriate way to address that? Having a default value isn't enough, because the formula still sees "" instead of "0".

Here is the criteria/formula:

my:QtyBlueTop * 4.5 + my:QtyRedTop * 10 + my:QtyMarble * 8.5 + my:QtyPurple * 4 + my:QtyGreen * 4 + my:OtherAmt * 0 > 24

If any of the fields are empty, the condition apparently doesn't evaluate as a number, and the conditional formatting doesn't evaluate as needed. (The actual numbers--4.5, 10, 8.5, etc.--will be replaced with run-time variables after I get this figured out... although that may be a challenge in itself.)

Is there a function I can wrap around each addend or value so that empty or null is treated as 0, or so that the formula uses 0 if the value is empty or null? Or is the solution more fundamental? (I know this is a rookie skill, but I promise I'll save the answer in my OneNote notebook this time!)

Thanks, Hillary!

**(Edited ten minutes later!):**

OK, so I just wormed around it by putting a rule on each text box that sets the actual value of the bound column to 0 whenever the value changes to null/empty. So, the question is now primarily academic: Is running a rule like that more "efficient" (great gobs of memory notwithstanding), or is it a better use of resources (the computer's, not mine) to rewrite the formula itself to check for nulls and use 0 instead? (Sort of a "give-a-control-a-fish or teach-a-control-to-fish" polemic.)