>>Are any of your index keys longer than 120 characters? This could cause a problem in your environment.
>
>Thanks for your kind attention, Fred. There is no such long indexes in the app. The longest index keys is 100 characters. And all of the indexes (about 150 .CDX) seems being changed to other collating sequence.
>
>However, I have used DISPLAY STRUCTURE to examine the problem data, and found all indexes are MACHINE collation. But it simply pops up "Collating sequence "PINYIN" is not found" everytime I try to open it in English machines. I really can't figure out what's going wrong.

In earlier versions of Fox (up to 5), there was a file called foxpro.int, and any non-machine collating sequence would pop up such a message if this file was absent. The content of this file was moved elsewhere (in 6 and later) so that's probably not it.

One thing you may need to check is whether there's a "codepage=auto" in config.fpw - this may cause Fox to try to apply the default codepage for the machine it runs on, and if that is Pinyin, and it can't find collation tables (which were in foxpro.int, don't know where are they now), it may give this message. Also, it may be using .nls files instead, so it may be worth checking if the .nls tables for Pinyin are present - they should be in the system32 directory. I don't know their names for Pinyin, but I figure you'd know that better than I do.