Hi,
Put the state 2 char codes in a table that you would use just for that.
That is data, not code, and that should not be part of the code. Having a
table, you can then enforce data integrity with some other tables at table
design level. Right now, someone cannot enter ZZ as 2 char code, if you use
the form you are designing, but if you use another form, data importation,
or edit the table directly, someone could enter ZZ, invalid data. If you got
enforce data integrity, not only a user won't be able to enter ZZ from your
form, but also from any other form, any way it imports data, and even if
someone edit the table directly. The name of the game is "relational
database", relational being about data in a table, not data in code or in
some obscure list in a control of a form. Make a table, just for that, at
long run, there are many more advantages that what... is there a single
problem having that data in a table?
Hoping it may help,
Vanderghast, Access MVP