I have several instances similar to this:
Lets say I need to store the instructor of a class. This instructor 90% of the time will be somebody who's listed in my "People" table. In which case my instructor field would hold the database ID of that person and the user would select it with a combo box.
What about the other times when the person is not (and should not be) in the people table?
I've gotten around this by having a text instructor field that the user can either choose from a list OR type in their own name.
However, if the instructors name changes in my People table now all those records holding that instructors name in a Course table are incorrect.
Is there a better way to handle this situation? Some method of storing a database ID OR a custom name?
Thanks
P.S. I don't need specifics, just a broad idea. I was thinking One field for ID_Person, then 2 more for Last Name and First Name. Handle the display on Forms/Reports. Good Idea? Bad Idea?