Setting up "lookup fields" in tables (which I believe is what you're talking about) is not as good as using a combo box with data from a second table. First, you're limited if you want to add/edit/delete items (hard to do programmatically) and second, if you want to use that information again in a second table, you really can't. The method I show in Access 201/202 is the best way to do it.

Setting up relationships using queries has several benefits over using global relationships. I talk about this in DEPTH in Access 220, but basically it's easier to use queries, and unless you need cascade updates or deletes, there isn't a great NEED to use global relationships IF you name all of your fields properly.