I can't help but jump in and say that VFP IS vulnerable to index corruption without even being on a network. Yes, it is a good thing to check the cabling, the network, switches, hubs, etc. and deter users from Ctrl-Alt-Del but do not say that VFP will not 'programmatically' corrupt an index.

I had a very interesting chat with a MS VFP rep a couple years ago at a DevCon regarding index corruption and provided a program that ran on a standalone computer which was capable of corrupting an index - Yes, I am saying that the program 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.

This MS Rep took my program back and put it on an even larger computer which would, in his words, spread the timings apart so that they could 'see' what was going on. The result was that, in fact, the index (CDX) was being corrupted due to VFP. The solution was to not recycle the last record in the table. 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.

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...


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