<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Double (teMulti) Byte Characters: Not able to view in Operating System - Microsoft</title>
    <link>https://community.hpe.com/t5/operating-system-microsoft/double-temulti-byte-characters-not-able-to-view/m-p/2835744#M2087</link>
    <description>One possibility could be with the ODBC module:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q234748" target="_blank"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;Q234748&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The article suggests setting the code page of the server to the code page of the data you will be working with.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jon&lt;BR /&gt;</description>
    <pubDate>Thu, 31 Oct 2002 00:56:23 GMT</pubDate>
    <dc:creator>Jon Finley</dc:creator>
    <dc:date>2002-10-31T00:56:23Z</dc:date>
    <item>
      <title>Double (teMulti) Byte Characters: Not able to view</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/double-temulti-byte-characters-not-able-to-view/m-p/2835743#M2086</link>
      <description>Hi Friends,&lt;BR /&gt;&lt;BR /&gt;I am able to view Korean/Japanese characters when doing reporting with the setup as below:&lt;BR /&gt;&lt;BR /&gt;Database: Sybase System 11&lt;BR /&gt;Reporting Tool: Brio Explorer&lt;BR /&gt;Connection Type: ODBC Connection&lt;BR /&gt;3rd Party Appln: NJStar Communicator&lt;BR /&gt;&lt;BR /&gt;But not able to view the Korean/Japanese characters when done reporting with SQL Server 2000 database with following setup:&lt;BR /&gt;&lt;BR /&gt;Database: SQL Server 2000&lt;BR /&gt;Reporting Tool: Brio Explorer&lt;BR /&gt;Connection Type: ODBC Connection&lt;BR /&gt;3rd Party Appln: NJStar Communicator&lt;BR /&gt;&lt;BR /&gt;Any idea as what might be the cause for this issue.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sanjay&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Oct 2002 04:19:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/double-temulti-byte-characters-not-able-to-view/m-p/2835743#M2086</guid>
      <dc:creator>Sanjay Verma</dc:creator>
      <dc:date>2002-10-30T04:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: Double (teMulti) Byte Characters: Not able to view</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/double-temulti-byte-characters-not-able-to-view/m-p/2835744#M2087</link>
      <description>One possibility could be with the ODBC module:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q234748" target="_blank"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;Q234748&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The article suggests setting the code page of the server to the code page of the data you will be working with.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jon&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Oct 2002 00:56:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/double-temulti-byte-characters-not-able-to-view/m-p/2835744#M2087</guid>
      <dc:creator>Jon Finley</dc:creator>
      <dc:date>2002-10-31T00:56:23Z</dc:date>
    </item>
  </channel>
</rss>

