Open Dataset non-unicode & default

[john_wayne]

Currently im using the open dataset with default then it hit a codepage error. I found out that the file contained characters that is not UTF-8 so when i changed the open dataset to non-unicode the codepage error goes away. Im wondering if there is any effect of changing from default to non-unicode.

[Former Member]

if your function keys working properly then please hit the 'F1' key on OPEN DATASET and read the SAP help of Open dataset-mode.

Cheers

Amit

[nils_buerckel]

Hi,

it sounds interesting that the error occurs with UTF-8 only (normally I would expect it vice versa) ...

Usually it depends on what you want to do with the created file.

SAP recommendation would be to use UTF-8, because then you can download most of the existing characters without problems (e.g. Chinese data and Russian data in one file).

In case of Non-Unicode, you are restricted to one code page (defined by logon language) and you will get an error once you need to download other characters (e.g. the u20AC-sign).

Can you describe which characters cause the error ?

Best regards,

Nils Buerckel

[former_member187983]

Hi

Look this link

[former_member187983]

Hi

Look this link

[venkatapavan_sinagam]

 
OPEN DATASET P_AFILE FOR INPUT IN TEXT MODE ENCODING DEFAULT ignoring conversion errors.

ADD ignoring conversion errors to ur prg

and should be unicode.

hope it will help you.

Regards,

sinagam.

Edited by: Venkata Pavan Sinagam on Sep 23, 2011 5:50 PM