Hi, J David.

Indeed, he did not address the StateT in any of these lessons in AX1 nor in the previous AB9, but you can apply the same technique he used on LeadSource or the others.

Maybe it was an honest mistake from Richard, maybe he left it as an Easter Egg : )... but it is a great opportunity in disguise so you can try to replicate that on your test table.

Did you have any problems trying to make that? Maybe we can help you with that.

Cheers!
Diogo Cuba

The State combo is an example of a simple "lookup" type table.  One that standardizes data entry.
That was covered in the Beginner 8 Lesson 3

You don't have to have a Primary key and link everything to a Foreign Key.  In fact there are instances such as this where you actually want to store some duplicate information.  Is it "perfectly normalized" - No.  There are times however when practical over rides theory.

Richard does a great job of explaining as you get further along.  For instance storing the address in an order.  You do want to do that as opposed to linking because of historical information in your data.  If a customer were to move and it's linked the order data would change.  When the address is stored in the order info you have a history of where that order was shipped.

Check out the Free video in the Zip Code Template for another example and more explanation.