I can't help but jump in and say that VFP IS vulnerable to index corruption without even being on a network.
Sure it is! I cannot recall one I have personally experienced in the last 3 or 4 years. The case this thread is addressing (i think!) has an index failure (if that is what it is) at a fairly high frequency.

do not say that VFP will not 'programmatically' corrupt an index.
That would depend a lot on how the program implements VFP. There are so many ways to solve a problem with VFP. Developers can take the macro approach and build views, field binding, input grids and use tabelupdate functions, or [a developer] could implement the discreet, subtler, low services the paradigm offers.

corrupted the index through constant and quick table updates which included deleting records and 'recycling' them for use. Buffering had no affect on whether the corruption occurred or not.
I would have to look at this program. Sounds like a macro-implementation with lots of selects and batch updating. Also, it seems that key [or index] fields were being changed a lot. If this was the case, it seems to break with what some might consider a 'best practice' (at least, to the very retentive): Indexed [or key] fields are typically written once, when they are added to the table.
But thats the appeal of VFP, you can write tight or you write loose. Many ways to solve a problem!

Now, having implemented that solution in our Call Centre (which runs 24/7 and handles in the area of 10,000 calls per day), the index corruption practically disappeared.
Wish an MS rep would help me sometimes: ).

Today, interestingly enough, I have recently upgraded our systems (which runs in 5 different locations) to VFP 7 SP1, the index corruption appears to be returning... So, question to Microsoft - Have changes been made in SP1 that would cause index corruption? I am totally open to providing routines which do full index testing (while systems are running) but I have yet to resurrect my IndexCorrupting program to see if SP1 may be the culprit - I will get to it though given the problems going on in the systems...

Are you rewriting existing key fields?

Terry
>
>
>Todd
>
>
>>The indexes are not breaking because of anything VFP is doing (or not doing). There are VFP solutions than run for years without index repairs.
>>
>>When you index - make sure to delete the tags and INDEX (not REINDEX). There was a thread on this a few days back.
>>
>>It might be good to hire a contractor to check and tune your network. At the very least, have your wiring checked. Try to determine why it is failing - VFP can be forgiving to a point - but you've got some connectivity issues making your app look bad (know what I mean) - so get it fixed before it becomes an embarassment :-)
>>
>>It would be a shame to spend all sorts of bucks and still have the same problem. Whats with the gigabyte file (shouldn't some of it be archived?).
>>
>>
>>>Thanks Sylvain
>>>
>>>The UPS is already in place, and so is the indexing happening after workhours but still i get this error.
>>>
>>>As for changing backend..i am trying to get it approved by the heads.
>>>
>>>What am i missing here ??
>>>Dinesh