If someone puts a note in field Note_03 on the Notes table, and there are no notes in Note_04-Note-10 then Note_03
That reveals a basic structural weakness to your design.
In a Notes table, each note should be in a different record, not in different fields of the same record.
You'd want a minimum of 3 fields in your notes table:
_fkGeneralTableID (link to serial number of specific record in General table
WhenRecorded--a field of type date or TimeStamp that records when the Notes Record was created
Note---text field to record actual Note
Then either a sorted portal or sorted relationship that sorts the related records in descending order by WhenRecorded will list the most recent update first--and there is no need for an added field to show that nor for a script to find the most recent note.
Thanks for the response. I'm trying that out and am currently working on the sorted portal section for a list view showing the most recent note for all tickets.