todd
your problem is more one of data analysis. it sounds like you are saying that a given supplier say, can supply several US states from the whole population of states.
in normal terms this would require 2 tables
- supplier table
- supplierstates table, which stores any number of states
now a multi-value field seeks to replace the supplierstates table with a single field in the supplier table, which can contain a number of values.
this is a non-relational structure, and may or may not be applicable. it does introduce problems of sorting/searching and maintenance that may or may not be resolved adequately. I do not know, as on principle i have avoided using the feature. for one thing, by being a non-standard feature, it removes any possiblity of migrating the access database to a different platform. in practice the feature adds very little. with experience the support structure for a proper lookup table can be in place very quickly anyway.