GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Microsoft
- >
- Re: Double (teMulti) Byte Characters: Not able to ...
Operating System - Microsoft
1850277
Members
3244
Online
104053
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2002 08:19 PM
10-29-2002 08:19 PM
Hi Friends,
I am able to view Korean/Japanese characters when doing reporting with the setup as below:
Database: Sybase System 11
Reporting Tool: Brio Explorer
Connection Type: ODBC Connection
3rd Party Appln: NJStar Communicator
But not able to view the Korean/Japanese characters when done reporting with SQL Server 2000 database with following setup:
Database: SQL Server 2000
Reporting Tool: Brio Explorer
Connection Type: ODBC Connection
3rd Party Appln: NJStar Communicator
Any idea as what might be the cause for this issue.
Regards,
Sanjay
I am able to view Korean/Japanese characters when doing reporting with the setup as below:
Database: Sybase System 11
Reporting Tool: Brio Explorer
Connection Type: ODBC Connection
3rd Party Appln: NJStar Communicator
But not able to view the Korean/Japanese characters when done reporting with SQL Server 2000 database with following setup:
Database: SQL Server 2000
Reporting Tool: Brio Explorer
Connection Type: ODBC Connection
3rd Party Appln: NJStar Communicator
Any idea as what might be the cause for this issue.
Regards,
Sanjay
Co-operation - The biggest chain reaction
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2002 04:56 PM
10-30-2002 04:56 PM
Solution
One possibility could be with the ODBC module:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q234748
The article suggests setting the code page of the server to the code page of the data you will be working with.
Jon
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q234748
The article suggests setting the code page of the server to the code page of the data you will be working with.
Jon
"Do or do not. There is no try!" - Yoda
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP