>>>For your information, I was in a somewhat similar position myself not so long ago. I took over an old application which used a lot of idx's. Since this caused problems, I had to get rid of all the idx files. I fixed this easily in a few steps:
>>>

• The first thing, is to find out which table uses an idx or more, and write down the their name(s) and index key(s).

>>>
• Add index tags for every table which uses an idx or more

>>>
• Search for "order" using GoFish, and change these lines if necessary

>>>
• Search for "Set index to" using GoFish, and change these lines if necessary

>>>
• Search for "Index on" using GoFish, and change these lines if necessary

>>>
• Delete all the idx files

>>>

>>>As always, don't forget to make a backup first, just in case...!
>>>
>>>Much to my surprise, it didn't take me more than a few minutes to do the whole conversion, on a very large application. Thanks to GoFish.
>>>
>>
>>Sorry for jumping in, but in dealing with old code something to keep in mind is that many people used only 4 characters for the commands, so you need to take into account "orde" and "inde" (I was never a fan of this shortcuts but I did find set inde to and set orde to or even use table orde tag...)
>
>I know, and I should have included the shorter version. Actually, the first thing I did with that application, was to replace all the shortened words with the full ones. That was actually a far easier job than I expected, mostly because it was an all prg project.

I do not realy see why not just using VFP's Code Reference. It allows to regexp, so the search for set\s+order?\s+to should be a simple thing.

Replace with the Code Reference is an other problem. If you go for prg and scx, no problem. With vcx it's a bit dangerous, there is a bug in the way vcx's are used (not in the Code Refernce, it only asumes wrong)