That would be a good approach. However, I was under the impression that one of the causes would be users turning off their computers while in the APP. How would I prevent that?

I'll do more research as to what can cause this and try to pin-point the cause.

>Why not take a different approach and determine what causes the index to be corrupted and fix that issue?
>
>>Does anyone have a good, quick, reliable way to identify an index as being corrupt?
>>
>>I've got an app that has an occasional problem with index corruption - but am relying on the user's to spot something wrong. I want to be able to tell them something is wrong - or better yet - fix it before they notice.