Well I thought I'd post how I've solved this to a fashion. Using the export log feature.
Firstly some news that the "Save As" function has a broken implementation of Unicode. When I started I was exporting the log files of jobs as .txt in Unicode and all the characters were being padded by two zeros in hex. This is broken functionality. Leaving extra spaces beween every character and extra new lines every other line. When I chose to export the files as Unicode UTF-8 these padded chars became normal chars.
After that little diversion I had an export of the log file. As you might know from the BackupExec view log section these are extreemly long (some 35 pages) and can be quite inpenitrable. However it does list each of the skipped files amungst much much more data.
There is a unix tool called Grep that can search a file and parse all the lines with a string in them, you can then have this redirected to a second file. So if you grep the log for for the word "skipped" boom you have a file with just the lines containing the skipped files.
Once you have the log file saved out from backup exec, run this command (yes it's a unix command, I don't know if there is an equivilent tool in Windows, there is not at a stnadard command prompt.) However there is an open source tool called grep for windows (I have not tested this solution though) available at http://gnuwin32.sourceforge.net/packages/grep.htm
I dragged the log file to my mac and ran this command at the terminal screen.
grep skipped logfile.txt > skippedfile.txt
This made a new file "skippedfile.txt" that list (as of this morning) all 427 files that were skipped from my full weekly backup.
I hope this might help others.