One particular client is having a problem where one particular table repeatedly becomes corrupt. It's a large table, but nowhere near the 2 GIG limit. We don't notice the problem until it's too late. The TABLEUPDATES say they are working, but once the file becomes corrupt, no data actually gets into the file. When we browse the file, we get an "INDEX does not match table" error. I believe this is running on WinNT and I'm mostly doing INSERTs to add records to the file. Does anyone know why this is happening or how I could prevent it?

Thanks,
Elyse