You have several parts in your proces. 1/ Eguide that is your front end interface is supporting utf8 as it is build in .NET. 2/ your sas system base/foundation is the one that executes the code can run in single byte mostly Latin1. It can also run in utf8 mode but in that case it should use other binaries. When it is on a server the SAS APP setting scripting os is the one doing that switch. 3/ there is an Access to oracle client software installed that must support the utf8 or the Latin1 encoding. This one is communicating with 4/ the oracle server and that database having defined some encoding fir the database and tables Having issues with thai you are most likely into some wrong configuration in the 2,3,4 aligning. Not an eguide issue but things that are used behind those.
... View more