Hi Ligs,
One of the basic rules of database design is that each row in a table should have a unique identifier. The purpose of that is to avoid ambiguity. In this case, Access has no way of knowing that you want to select the 3rd John Smith rather than the 5th John Smith. It just knows you want John Smith, so it presents you with the first one in the table.
I don't know if you have a unique identifier (such as a unique number that is automatically generated by Access) for each record in your table. If you do, then you'd need to bind your combobox to that unique identifier rather than to the name. You can still choose to display the name in the combobox.
If you don't have a unique identifier, then you really need to create one in your table. This can be done by adding a single field and having Access autogenerate a numerical unique identifier for each record. Alternatively, you could create what's called a concatenated key. A "key" is simply a unique identifier for the record; by "concatenated," we mean that you select more than one field as the "key" so that together the two or more fields uniquely identify any given row. For example, in your case you might have "Name" and "Phone Number" as your concatenated key. You may have more than one John Smith, but chances are you don't have more than one with the same phone number (well, unless it's father and son!...that tells you why it's a good idea simply to use a sequential autogenerated number to identify each row). But this all raises a question, how is your user supposed to know which John Smith to select from the combobox? If you go with the concatenated key idea, then you should include all the fields that make up your concatenated key in the drop down too so that the user doesn't have to pick John Smith by trial and error.
Good luck!
Blaine