Yes, relationships would help. For just the report, this can be done in the
query. Instead of basing the report on the Transaction_Records table, create
a query and include the Transactions_Records table and the Purchaser table.
It appears that the combo box is supplying the ID number of the record from
the Purchaser table to the Transaction_Records table. In the query, drag and
drop this ID field from one table to the same field in the other table. This
will create a link between them. Next, add the fields from the
Transaction_Record table that you are using in the report, skipping the
linked field. Instead of the linked field, add the Purchaser's Name field
from the Purchaser table to the query's output. This will give you the name
instead of the ID number. Reset the textbox in the report to use this name
field instead of the field it was using. Since the rest of the fields are
the same, once you set the Record Source of the report to the query, the
rest of the controls ought to be ok.
Just as a warning, don't use "reserved words" as field names. The most
common use of a reserved word as a field name is naming a field "Name".
Instead call the field PurchaserName, CustomerName, CompanyName, FirstName,
LastName, etc. While you can get by with using reserved words as field
names, if you aren't careful, it can cause you problems. Reserved words are
any word that Access recognizes as a built-in function, property, method,
collection, or constant. Another common example of a reserved word that gets
used as a field name is "date".