I think your plan of purchasing Stonefield Database tookit and FoxExpress (VFE) is a good one for MANY reasons, however, I'm not sure if that will fix your problems with indices--it will however, make it much simpler to develop your apps, upgrade your tables when you push out app updates, and fix your tables at the customer's site. You need to get to the 'root' of the problem: why your indices are getting corrupted in the first place. I use VFE FoxExpress for all my apps I develop personally (having learned it while employed at my last job and I love it), but at my current job I use vanilla VFP and Foxfix. I deploy the foxfix5 dll with my app to repair tables and indices on the fly which works fine; but honestly, I don't have that many problems with corrupted indices except in the peer-to-peer environment in Win98 with some of our customers. I don't know when the last time we had real problems with corrupted indices in a true client-server or even with the database stored on a true network NOS like Novell or Windows 2000 was-it's been awhile! We have a commercial app that is used at hundreds of sites with users ranging from 1 to 20 in a myriad of topologies.

Tracy


>I like programming with Visual FoxPro, but indexes give me a heck of a hard time. I work with database contained tables, with free tables, in one computer, in client/server, you name it. It's always a problem when it comes to repairing corrupted indexes. I'm planning to buy Stonefield Database toolkit and F1 Technology FoxExpress, but want to know if I will stop having problems with indexes. Some one can give an opinion.
>
>Thanks a lot.
>
>Luis Flores