That'll be great Todd.

There's not 'rush' of course...

cheers
Jim

>>Hi Todd,
>>
>>I see that JimS of Microsoft has asked you to e-mail him the sample code that corrupts.
>>
>>On the other hand, if the code sequence involved is even modestly 'standard' (i.e. would be commonly done similarly by more than a handful of developers), it might be most enlightening to share it here. At the very least more of us would be aware of another dicey coding situation.
>>
>>cheers
>>
>> >>Something we all should be doing on a regular basis is rebuilding Indexes. Simply relying on the REINDEX command is not necessarily the best route to go. Ideally the Tags should be dropped and recreated from scratch. This is a problem if the Tables are referenced by a DBC and have persistent relationships / Primary Keys / Candidate Keys or if you have systems that really do run 24 by 7.
>>>>
>>>>For a couple of months now some of the FoxPro community’s leading luminaries have had access to a utility I created that facilitates SHARED mode recreation of Indexes. I am now looking to find additional people to put this into their production systems and who are also willing to provide testimonials.
>>>>
>>>>Feel free to reply either to this post or using a private message.
>>>>
>>>>Regards to all,
>>>>Houston.
>>>
>>>Count me in on this too!
>>>
>>>I have been constantly plagued with index corruption that many users have constantly blamed on bad network cards, cables, this, that and a host of other things without admitting that VFP has a major index corruption problem and it is in the Visual FoxPro software itself! I have even sent a program to Microsoft that builds a table and, using standard VFP syntax, corrupted the index. Single computer - single program which does not even bring in multi-user systems or buffering let alone a 24/7 system with a dozen users. Hopefully Microsoft will wake-up and resolve these index issues soon as they have been a plague since v6 and only getting worse by the release.
>>>
>>>
>>>Todd
>
>Jim,
>
>I am pulling everything together for everyone to examine as it is a cornerstone to our system running 24/7. I had broached this subject several years ago and raised it with Doug Shepard (Microsoft) at a Devcon in Palm Springs (La Quinta) who took the code back and did acknowlege that there was a problem. Now, the sample that I had was written with VFP6 so I am just digging it out of the archives and getting my IndexTester program together for all but I can tell you that I suffer continual corruption (especially with an index on deleted()) in the system updated to VFP7 and another totally separate system (on another network) written in VFP8. I just need a few days to pull things together.
>
>
>Todd