You can do whatever you want. IMO, replacing the FK field with the Names is the wrong way to go. You shouldn't/don't want to duplicate data. Let's say the PK value 2 is "Robin Child". She gets married and changes her name to "Robin Thompson". Now you have to go through all records (and all tables where names might be) and change her name. If you used a numeric FK, all you have to do is change her name in 1 table.
In fact, you could change her name to "Banana Pudding" - nothing else has to be changed.
You didn't include your table "tblInspectionType", so I had to create my own. I copied the "InspectionTypes" data from the table "tblInspectionReports" into Excel. I ended up with 5 columns, so I moved all to one column. I sorted the column, then deleted the duplicates, which I exported as a text file. I imported the text file into Access.
Then I created a query (2 c0lumns-> SELECT tblInspectionReports.DIRID, tblInspectionReports.InspectionTypeFROM tblInspectionReports
and saved the results in a text file. I wrote a small routine to parse the text file and inserted the data into "tblInspections".
Yes, I would get rid of the MVF.
No. That would violate the rules of normalization. In some table, you have "Location1", "Location2", "Location3". Repeating fields is a sure sign of violating the rules normalization. What happens if you need to add 2 more locations? You have to modify the table, the queries, the form and the reports. If "Locations" were in their own table (many side), you just have to add the new data.
Same goes for "InspectionTypes".
Rules Of Normalization poster.