A family of Microsoft relational database management systems designed for ease of use.
As a rider to John's reply, you should not be storing the same name in multiple rows in one table. This risks inconsistencies, something to which I can personally testify, having in one database found three versions of my own name as author of technical articles in my own field of work. The people should be in a separate table with a numeric (e.g. autonumber) primary key and text columns for the names. This table will have one row per person so there can be no inconsistencies. The table to which your form is bound should have a long integer number PersonID (or similar) foreign key which references the key of the people table.
It's a simple task to insert the distinct names from your current table into a new people table with an 'append' query. You can then easily update a new PersonID column in your current table with an 'update' query. An enforced relationship between the tables can then be created. Once you are satisfied that the new data is correct you can delete the redundant name(s) columns from the current table.
In your form you can use a combo box for the person, and put code in its NotInList event procedure to enable you to enter a new name into the people table directly from your form. You'll find examples of how to do this in various contexts in the file NotInList.zip in my public databases folder at:
https://skydrive.live.com/?cid=44CC60D7FEA42912&id=44CC60D7FEA42912!169
You might have to copy the text of the link into your browser's address bar (not the link location). For some reason it doesn't always seem to work as a hyperlink.
To carry the person forward in your form from one record to the next will still use John's code exactly as he posted it.