>Really, that's not a good use of try/catch. It's hiding the issue instead of showing you where it is so you can fix it.
>
>You just as well put in this line:
>
>ON ERROR *
>

Just putting dust under the carpet... But you haven't read everything. ON ERROR... probably would show the same error I had to hide under the carpet...