FilterValues ( ValueListItems ( Get ( Filename ) ; "Yourvaluelistnameinquotes" ) ; Yourtable::StateAbb ) will return the value of StateAbb if it is in the value list and null if it is not, but I would not use such value lists myself.
I'd create a table where each record lists one state and a second field gives the region.
Then a relationship like this:
YourTable::StateAbb = States::StateAbb
can be used to display States::Region on your layout to give the region.
I'd also use this States table for producing all the region based value lists by setting them up as conditional value lists.
Thank you Phil. Does this solution still work each record will contain several different state/region entries (E.g. college, graduate school, home address and each location of work experience)?
You could still do it if you define separate relationships for each-- to different occurrences of the same Regions table, but I'd put that list of different state/region entries into a related table also. That gives me just one relationship (LocationList to Regions ) and also adds the ability to enter a flexible list of such location records.