A family of Microsoft relational database management systems designed for ease of use.
You might like to take a look at Normalization.zip in my public databases folder at:
https://onedrive.live.com/?cid=44CC60D7FEA42912&id=44CC60D7FEA42912!169
If you have trouble downloading a specific file, clicking on the 'Download' button at the top of the page while no files are selected should download a zip file of all files in the folder, from which you should then be able to unpack the relevant file.
This little demo file provides as simple as possible, but no more so, an introduction to the subject of normalization by decomposition. In the first instance concentrate on the first three normal forms, in particular Third Normal Form (3NF), which is pertinent to your issue. Note how only CustomerID is stored in a column in the Orders table, as my colleagues here have explained.
The demo includes an example of a user interface, made up of a form and subform, for entering data in this context. As you'll see the combo box for selecting a customer shows the names but is bound to the CustomerID foreign key column in Orders, just as in your case. To insert a new customer the form includes a button which opens a dialogue form, rather than allowing the user to type a new name into the combo box and using code in the control's NotInList event procedure to insert a new row into the Customers table. This is necessary because personal names can legitimately be duplicated.