>
>Thanks Craig for taking a break from the T-Day preparations. Your article has a number of good ideas on defending against the rude exit. Have you come across any "corruption on the fly" before. My process can run for weeks (24 Hr 7 Days/Wk) then start getting lost. The fix is always a fresh index, and there is never any corruption in the index header. I've tracked it down to the recycle routine, and the trigger seems to be something that I have failed to protect against during periods of VERY high contention. I could see 6 or more processes going after the same record at the "same" time, (and then the same next record if they can't get a lock).
>
>Bob

Yes, I've seen that before.