W
Walt
We are using ASP.net to develop a new website. The old website uses
legacy ASP connecting to an Oracle database (9.2, W2k3, charecter set
WE8ISO8859P1). The new site connects to the same database but using
ASP.NET.
Our problem is that extended characters are printing out as question
marks. In particular, the "smart quote" characters that MS Word likes
to use are showing up as question marks.
We ran into a similar problem with the legacy ASP about a year ago and
solved it by changing the registry entry
HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/HOME0/NLS_LANG to
AMERICAN_AMERICA.WE8ISO8859P1 so that it matchs the character set on the
database.
Any clues how to fix it in the dot.net world?
Thanks.
legacy ASP connecting to an Oracle database (9.2, W2k3, charecter set
WE8ISO8859P1). The new site connects to the same database but using
ASP.NET.
Our problem is that extended characters are printing out as question
marks. In particular, the "smart quote" characters that MS Word likes
to use are showing up as question marks.
We ran into a similar problem with the legacy ASP about a year ago and
solved it by changing the registry entry
HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/HOME0/NLS_LANG to
AMERICAN_AMERICA.WE8ISO8859P1 so that it matchs the character set on the
database.
Any clues how to fix it in the dot.net world?
Thanks.