To me, this sounds like there is a
LOOK UP FIELD in table "Purchases". (not a good idea - see
The Evils of Lookup Fields in Tables)
This is why experienced programmers never use Look Up FIELDS.
It is a little confusing (without knowing anything about the design)...the column alias is "Taught By", looking at the table "Purchases", trying to get a name.
Is [Pro/Staff Member Name] a FK to a table of Staff Members?
Why not add the Staff Members table to the query , link the PK/FK fields and add the First & Last names to the query design grid?
--------------------------------
Suggestions about naming objects:
Use only letters and numbers (exception is the underscore) for object names.
Do not use spaces, punctuation or special characters in object names.
Do not use Look up FIELDS, Multi-Value fields or Calculated fields in tables.
Do not begin object names with a number.
Object names include: fields, tables, queries, forms, reports