|There are multiple things we could do, such as|
1) ignore errors and move on, we could even record on which file the error was reported
2) this would be my preference
Go through each shape on the last slide and perform some checks, this is where we need to understand what commonalities the tables you want the data from have and what the other tables you dont want data from have. For example
if you had three shapes on the last slide and two of the tables had the word 'Mouse" in it somewhere, we know we can ignore these tables and pick the value from the remaing table as long as the word 'Mouse' does not appear on it.
or if we know that the words you want will either be "Cat" "Dog" "Rat" or "Shoe" we can once again go through each shape, check if the word exists and return it.
It is not always easy to stop the execution of code and amend it, then continue from where it failed, there are far better ways to make your code more robust as per point 2.
Have a think and perhaps you can send me a couple of the presentations to look at over email? i can PM you my email address if you like.
Please note that i will be on training for the next couple of days and will have very limited access to a PC.