>>
>>See CPCURRENT() in help.
>
>Fred
>
>Yep, its mentioned their allright but it still doesn't really address what effect the different settings might have or what the possible settings are. If I read Paul's reply correctly, the auto setting converts the stored (in the dbf) codepage to the displayed codepage and vice versa. While chapter 18 in the DG says that VFP does the conversion, it doesn't say anything about their being a CONFIG.FPW setting that will change how it works. I also thought it might be a SET command so I searched their too and came up with nothing.
>
>Sorry, I don't mean to sound like I'm venting, I just wanted you to know that I really had searched the documentation.
>
>Donny

The CODEPAGE = AUTO or CODEPAGE = < any specific codepage > affects the behavior of VFP when it creates new tables, .??x files (forms, classes etc), i.e. it sets the default. However, the codepage info for a specific table is stored in its table header (29th byte), and overrides this setting. You can freely mix tables marked with various codepages in the same app; they will be translated appropriately (both read and write). This may eventually fail (theoretically) if your system lacks appropriate .nls files for a specific codepage, or codepage combination.