>>Yeah, network problems are really a problem because it's always our apps that die and so the problem MUST be with our apps. :-) I really don't have a clue, and of course, the real issue is to track down what is corrupting the index in the first place. Does this program run all the time? I ask because we have a mail-scanner program that runs all the time and it was dieing on us at various off-hours times with weird problems like corrupted memos, "can't find config.dbf" when there is no config.dbf and is never referenced in the program. We finally decided that when nightly/weekend network maintenance of some type ( backups, etc. ) were being performed it was conflicting with our program trying to access the files and killing it. We finally set up the program to 1) only open the tables when they are actually needed instead of leaving them open all the time, 2) put the program into a hibernation state from 8PM to 6Am every night and 3) put it into hibernation on Saturday and Sunday. It
>>seems to be surviving at this point. One point, this program runs in Netware 4.1a environment but Win 3.1 OS. Don't know if this helps at all but it must be network related somehow. If the network guys can't/won't help find the problem maybe you could form some kind of workaround like we did. Wish I could help more. Anything else I can check on for you, let me know.
>>
>>Bill
>
>The apps is run on a daily, but not continuous basis. As I mentioned to Ed, this seems to be occurring after a new set of index tags has been re-built. I've checked the routine that does this, the information, and nothing's changed (except the OS). So I've got routines that after 5 years of bug-free operation in quite a few apps all of a sudden that have developed bugs. Right, and next year I'm going to be playing shooting guard for the Chicago Bulls.:-)
>
>I've made a modification (adding a FLUSH) to see if that helps, but it really should be unnecessary. So I'm not terribly hopeful.:-(
>
>Thanks, however, for the info and suggestions.

I hope the final answer surfaces, but it's hard when the problem is outside the scope that you can practically affect ( i.e. OS, network ). Be sure and send me tickets to your first game. :-))

Bill