perhaps you shouldn't be ignoring errors in the first place... that's what this code does:
Code:
        Catch ex As System.Threading.ThreadInterruptedException
        End Try
THat's where those are coming from... personally (and this is just my opinion) I'd remove the error handler for the moment, let those exceptions happen... find out WHY they are happening, and then attempt to re-structure the code so that the error doesn't happen in the first place.

And then I'd vow to never ever again use an empty catch to ignore exceptions.


-tg