Unrelated to the question but in post #1, your T_Engineer table contains a field for EngineerFullName, that is not necessary to store that since you are already storing the first and last name already. Just use a query to create the full name where needed.
I also see the possibility to eliminate the long text field by using a Notes table that just splits up all those individual note entries into smaller sensible components. Then, when an actual update is made, it is in a subform that has the NoteID, ProjID, NoteDate, Action, comment. Using a query could piece all those parts back together for display on a form or in a report.
Here is an example of one that I use. Of course this assumes that no individual comment would exceed 255 characters. If that happens, I usually just split the comment into two different notes as required.