So i have tables where fields will have to be selected between a fixed set of values.
Lets say a delivery of a Package of a book can be either "normal", "urgent" or "VIP".
Access allows this through the creation of fields with the Lookup Wizard.
The question is, OUTSIDE Access, should i make always tables for such fields or just validate through constrains, or through application level?
I ask because the application that I'm making is likely to be migrated to another Database system and i want to make life easier for whoever takes the job in the future.

Tnx ppl!

its things like that that make defining lookups at table level not recommended. simply store an integer value (ie 1,2,3) in the table. I always use longs, irrespective of the expected range

have a separate 2 column table storing the lookupid, and the delivery option.

and design your own combo or list box. It's trivially easy, and avoids all complications.

you often need a slightly different combo to the wizard anyway - maybe presented in a different order, or with an <ALL> option - so you often have to design a custom combo box anyway.