I have a web application that I recently converted to ASP.NET 2.0
This application displays Japanese characters. SQL Server 2000 is the database.
I have another classic ASP application which updates the database.
The database has 2 tables
Table 1
title varchar(40)
Table 2
title varchar(40)
( yes.. I should be using unicode and nvarchar in the firstplace to store japanese character).
I do realize that this is not the correct way to store japanese text. This is an application that was written years ago and there's way too much data now - I just can't go back and change the database design.
Page1.asp updates Table 1. Charset is :iso-2022-jp
Page2.asp updates Table2 No charset has been specified.
The web Application retrieves this data and displays it.
This is the code that I use to get these nonunicodebytes. ...
Go to the complete details ...