>We have a French-Canadian client who is currently upgrading from our Dos version of our application (Clipper-based) to our VFP version.
>
>I've written a conversion routine which handles the upgrade of the data. All of our VFP tables use a code page of 1252. In some of the older Clipper data, there are some international characters being used that do not get translated/copied over properly.
>
>Could someone please tell me how to properly handle this so that our current code page remains as is (1252) and all their text gets imported properly?
>
>Jon
This should be done automatically, if the table is marked with the correct codepage. Perhaps you can open the table with VFP, and mark it with the correct codepage for DOS, for instance, 850 or 457 (???).
If the table is already marked with an incorrect codepage, you may need cpzero.prg.
At least, this is the way it works for FoxPro/DOS tables. Perhaps you can copy it to a FoxPro/DOS table first.
You might also take a look at cpconvert(), to do the conversion manually.
HTH, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
