>After more verifications, I found that this one was giving the same error as the one I am trying to troubleshoot but it was not related. The other one still has the same schema such as happening at random basis.

But what was the reason for the first one failing? Was it data-related? Was there something in the data itself that caused it to fail? Could that same data issue be causing other failings as well?

~~Bonnie



>>OK, so here's what I would do. Put back the record that *always* crashes. Put in a counter and an if counter = 525 (or whatever record it is) and then put a breakpoint on a dummy statement after the if. That way you only break just when you hit the record that always crashes. Then as you step through it, you should be able to see exactly *what* is not correctly instantiated and hopefully you'll also see why.
>
>After more verifications, I found that this one was giving the same error as the one I am trying to troubleshoot but it was not related. The other one still has the same schema such as happening at random basis. So, it is difficult to use the breakpoint approach in this case as this is happening only at about a few thousand hits. It is also not happening on the same data process. It can happen at the logging process, in a schema process, in a SQLExec, etc. That is why I thing this is related to the other bug.