Richard,

I recall in an earlier class on table properties you mentioned that you are not particularly fond of lookups for a field from within a table.

With the combo box you added for LeadSource within the CustomerF form, couldn't you set the LeadSource field in CustomerT to a combo box bound to LeadSourceT so that when it is pulled into the CustomerF form it was already set up?  What I am really asking is if there is a downside to doing it this way. I know you mentioned that you don't always show us the best way up front, and I am actually thankful for that because it does help to have an understanding of all the different ways something can be done.

But I would like to know if setting up a combo box bound to a source table for a field in a separate  table is something that you do not recommend and the reason why.  

Thanks and great job with this series. I am learning a lot.
Christian

---

Reply from Richard Rost:

I don't like lookup fields in TABLES because when you get into more advanced stuff like VBA programming, recordsets, SQL, etc., they because ALMOST IMPOSSIBLE to work with.

Now... setting up the form's combo box so it pulls records off of another table IS exactly what you should be doing... and I'm going to take you through a couple of different INCORRECT iterations of this between Access Beginner 8 and Expert 1, where I show you how to do it PROPERLY.

Like you said, I'm building up your appreciation for WHY the correct way is CORRECT.