>Hi there,
>
>I'm working on a VFP 7.0 application that uses the VFP 7.0 database as the back end. The front-end application runs on Win9x operating systems as well as Win2000. Each site has multiple client workstations (5-150) and a server; the latter has the database container and tables on it. I am located in the U.S. along with most of my customer base. But one of my sites is in Japan. This past weekend, I had them run a compiled exe that contained a *.prg which added a few new fields to a couple of the tables and an additional index to another table. This exe was run from one of the Japanese clients that runs Japanese windows.
>
>The problem is with the newly indexed table: the Japanese Win9x clients were unable to access this table, but the Win2000 clients seemed to have no problem with the table.
>
>For production reasons, I had the Japanese plant revert to the older, backed-up copy of the database so they could successfully collect data. Meanwhile, prior to getting the older database in the production environment, about 700 records were saved to the new database, and I need to import these into the current production database. From the VFP 7.0 development environment on my Win2000 laptop, I'm also unable to open the re-indexed table... getting the following error: "Collating sequence 'JAPANESE' is not found." I discovered some information on CODE PAGE and SYS(2300) and SET COLLATE command, but no matter how I have my environment set, I still can't access that re-indexed table.
>
>I have two questions:
>
>1) How can I access the table with the new index, and
>2) How can I successfully index the table in the future in order to avoid repeating this scenario? Do I need to do this from my development environment, or can it be done from a Japanese client?
>
>Any and all suggestions are welcome!
>
>Joe

Joe,
Have you tried with :
Codepage=932
in config.fpw.
Cetin