>One of the things I was pleased to see in vfp was the ability to
>rearrange the order of indexes in the same way we could already change
>the order of fields. Experience has taught me that, once you've got more than about 25 fields in a table, any order other than alphabetic makes it almost impossible for the end user to navigate the fields in searches and queries etc. The same applies once you go past about a dozen indexes. But these have, in my case, often been added ad hoc over years as an application has developed and my users demands have increased.
>
>As is the way with end users, they didn't make their demands in
>alphabetical order!
>
>So I looked forward to adapting my FP2.6 apps and tables to
>the new format and taking this long awaited opportunity to tidy up my
>index arrangements. But having spent 20 minutes repositioning the 24 indexes in one table - twice (because I assumed I must have hit a wrong key the first time) - I find that although it will let you go through the motions, it doesn't actually save the changes! What kind of deal is that?!
>
>Is it me? Or is it VFP?
>
>Harry

Ditto DF's reply concerning interface. But if you find you must rearrange them in the cdx, you could destroy the cdx and recreate them from scratch. Gendbc or my gentable utility (here in the files section) will both give you a code listing of the existing indexes, you could cut and paste the code so the tags are created in the desired order.

BTW, if you don't mind me asking, where is your coutry? I have never heard of it before seeing your posts. Very interesting name and flag...