Data entry should never be done directly into tables or queries even if it is for your own use. Using a form gives you the ability to add functionality and to ensure that the data entered is valid.
Here is a sample app that shows three ways to display data from your lookup table. Two of them include saving the data in a second table but you need to look long and hard into the need for this. In my experience, the only reason to copy data to a second table is because you want to capture a value at a point in time. The most common example is copying the Price in addition to the ProductID when you are creating an order. You want the price at the time the order is placed, not what it is tomorrow. There are other ways to do this with history tables, but the simplest solution in this case is copying the Price and copying data at a point in time does not violate normalization rules because when the price changes, you don't want your copy to change. You want it to remain what it was when you copied it.
I don't think age and telephone number fall into that category and you would probably not want to store age in any event. It would be more reasonable to store birth date and calculate age on the fly. My age today can be different from my age yesterday or tomorrow if I pass a birthday. If data can become invalid based on the passage of time, do not store it.
