Working from a very limited understanding of what you have here, there appear to be a number of issues.
your perform quick find step would be:
Perform Quick Find ["DCA 01"]
and this will search all quick find enabled fields of the current layout for this text, so this may not be what you need.
See this link for examples of scripted finds that may be a better option: Scripted Find Examples
And it appears that you have multiple field,s each for a different cable. This structure complicates what you are trying to do. If you set up a related table for this purpose with one field for the cable name and another as the foreign key to your original table, a relationship that matches by cable to your log table could match only to records for that cable and could be sorted in descending order by date so that you could use the relationship to match to the most recent log entry for that cable.
In regards to your last para, the problem is that I am trying to build one page so that at a glance, we can see where each cable is located. For a little more info on them - they are cables with custom underwater communications boxes attached and the boxes fail on a regular basis so teh cables are swapped out for repair and often not returned to their original position (as we have used a substitute cable to fill that position) so tracing them is essential to see what sort of lifespan each box has and whether it is a particular user who is breaking them etc.
Not sure if that helps explain what I am after here?
I am trying to build one page so that at a glance, we can see where each cable is located.
That can still be done even if you use a related table as I have recommended.
Thanks Phil. I will start working on it today!