No, you need to put the rules on the text boxes, but the logic is quite
complex and all will be trying to set the value of field 467, so things might
get messy.

Example for 1 rule:
If field466 = A and field462 = isblank then concat field466 and field464.
Result "AU"

Create the same rule on both field 466 and 462 as follows:
Action: Set a field's value, field 467, concat(field466, field464)
Condition: field466 is equal to A AND field462 is blank

To make sure that rules always fire, you can first use an action to set
their value to an empty string, and then a second one to set their value to
the real value. So for your 202 checkbox, you can create a rule that will set
466 first to an empty string, and then to an A. This will ensure that any
rules defined on 466 will always run. The reason for this is: If the value of
a field does not change, the rules defined on that field won't fire. By
emptying the field first, you force the rules on the field to fire.

If that does not work, you can always create a helperField that can evaluate
all the values of the text fields and set the value of 467 accordingly. You
can make the rule on this helperField fire at all times by creating 1 rule
with 2 actions on each of the other fields to set the value of the
helperfield to a string (e.g. "test") in the first action and then to an
empty string in the second action.

As usual, I'm giving you ideas on how to get things done and haven't tried
it out myself. If you get stuck, let me know, and I'll test it out quickly
for you.
---
S.Y.M. Wong-A-Ton