>>>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
>>
>>What version of FP?
>>
>>If this is a Novell network, there were problems with FP tables becoming corrupt depending on what client ( Novell or MS ) was being run on the workstations. There have been threads here on this you can search on and you might try searching Novell's site.
>>
>>Bill
>
>I'm using VFP6. The client is using an NT network, not Novell.

Hmmm ... I'm sorry Elyse, I don't know then. Would seem to be a network issue since VFP via the TABLEUPDATES() thinks things are ok. Hopefully someone with some experience with this specific scenario will jump in.

Bill