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.

~~Bonnie




>>Maybe there's something screwy with record #525?
>
>I removed it and the same thing happens a few records later. I cannot find the pattern in all this. What I know is that this is happening about four times a week, causing errors in the application, at various levels. One level is at every hit where we update a field in the user table. There is no error in there. This works about 25000 times in a row. But, on a particular hit, I have this irritating error message.