Validation Rule question

[Sue Virden]

I have a field where I store the reason for update of a record. The valid
entries are I for Initial entry, A,E,P,N for Address, Email, Phone or Name
Change. My validation rule is
Is Null Or "I" Or Not Like "*[!a,e,n,p]*"
This works. Unfortunately I'm not sure why.
However, we used to use NE for new entry (we have now changed that to I) and
AC, NC etc for the records that have been changed. I would like to be able to
require a C after the combination of AENP characters to eliminate the
possiblity of someone entering NE for New Entry when indeed it will now mean
Name Address change. Is there a way to modify this rule to force a C after
the change characters?

Thank you.

 

[Allen Browne]

1. Create a small table with one text field, marked as primary key.

2 .Enter a record for each value entry.

3. Create a relationship between this table and the field in your existing
table. In the Relationship window, check the box for Referential Integrity.

This restricts the entries allowed to those in the little table you just
made, so you no longer need any validation rule. You can use this little
table as the RowSource for a combo box. If you decide to add another entry
to the little lookup table later, there's nothing else you need to change to
make it work.

Most database applications have several of these little lookup tables in
them.