I have read many experts say that lookup fields create problems and they stress not to use them. As far as wizards are concerned, I don't believe the web languages have these kinds of things, do they? If they do, I've never used one.
If you create a combo to do a "Lookup" on a form to return either a value or a reference to that value, you run into no problems.
If you tell ACCESS that you are doing a lookup in a table, then ACCESS will return the value or the value associated with a reference WITHOUT telling you which is being returned. Means when you are reviewing your data in a table and you see "Red" in a field that is a "Lookup", you are not sure if the actual value saved is "Red", is a pointer to the first instance of "Red" in a looked up table, or a different pointer to another instance of "Red" in a looked up table. Makes it much more difficult to debug issues when you have issues with data.
On the down side, for ACCESS, it has features that I personally don't think add value for end users. On the plus, it is far better than dealing with something like .PHP, C, or VB for rapid application development. Not as handy as Clarion, but a pretty decent environment once you get use to it.