This is caused by the CCSID in your files being incorrectly set to 65535. If you have Client Access V3R1M3 or higher, select "File.. .Properties.. .". Select the "Conversions" tab and select "Convert CCSID 65535".

If you have an older version of Client Access, use the INI file technique described in the other messages.

---

Create the file CWBTFR.INI in the Windows directory with the following contents;

[Client Access Data Transfer]
ForceTranslation=1

---

Create a file named CWBTFR.INI in the Windows directory. In it put exactly:

[Client Access Data Transfer]
ForceTranslation=1


Then CHGSYSVAL QCCSID and change that from 65535 or *HEX to the ID for your language ( 37 for US English).

---

This happens to me when character fields are coded with CCSID(65535). I fixed this problem by:

1. Changing my interactive job CCSID to the correct value (37 for US)

2. Recompiling the file (after a back-up)

3. Checking with DSPFFD that the character fields are coded with the correct CCSID

---

Yes, that is a lot easier, but make sure the CCSID is not still set at the default of 65535 or you will ForceTranslation right back to no translation. Also, changing the CCSID will create files with that CCSID (such as 37 for US English) from then on.

---

Perhaps it might have been easier. But the way Robin fixed the problem is the 'correct' way of taking care of this and it could save some hassle down the road.

---