Hi,

Our school has an application in which :
- Teachers enter comments through a web interface built in asp (not
asp.net).
- Comments are stored in a SQL server 2000 (in a nText field)
- Comments are printed through a MS-Access 2002 front-end...

Most comments are in English, Spanish or French. Some comments are
English + Japanese.

- The Japanese teachers can enter their comments through the web
interface without any glitch.
- The comments are obviously stored properly in the nText field, as
they can be displayed through the web interface.

Here is where problems start to occur...

- When browsing through the table using the Enterprise Manager, the
comment appears blank if it contains some Japanese.
- When browsing through the table in Access (the table being linked),
we can see the series of unicodes :
漢字テス... while, in the next paragraph, the
English text is perfectly readable...
- Similarly, on the printed report, the Japanese text appears as a
series of Unicodes, while the English text appears perfactly readable.

If I copy the Japanese text from the web interface and paste it into
the linked table in Access, it displays perfectly and prints perfectly
in Access. But of course, I can't do that manually for all students...
However, if I now look at the same record through the Enterprise
Manager, I see the text (at last !) but only as a series of unreadable
characters. I can imagine that that last problem is due to a lack of
Japanese font in the Enterprise Manager, bacause if I copy these
uneradable characters and paste them in the original web form, they
display perfectly...

I would really appreciate if someone could help me sort out that
problem.
Many thanks for all ideas.

DL

DL (lalouxd (AT) isb (DOT) be) writes:
What do you see in Query Analyzer?

Do you actually see the ampersand, hash mark, digits and semicolon?
In such case, I would assume that the page writes that do the database.
The browser will present those codes correctly, but obviously Access
will not.




--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

On Feb 21, 11:58 pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:

Hi Erland,

Yes. I see the ampersand, hash mark, digits and semicolon.
That's actually a good point. It would mean that the problem is with
the communication between the asp pages and the sql server : asp that
would let the user type Japanese characters in the text control, but
the typed text would be translated into the sequence of ampersand,
hash mark, digits and semicolon...

That would also explain what I discovered after having posted my
message : I went back to similar data that was entered in an Access
database last year and years before, using Access as a front-end. The
Japanese text always printed properly and was never a problem. I
transfered it to the sql server and looked at it through the new web
interface : it displayed as series of question marks (?????80%????...)

Do you by chance know how I could eliminate that problem linked to the
web interface or do you suggest I post the question on an asp list ?

Thanks for helping me clarify the source of my problem,

DL




On Feb 21, 11:58 pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:

DL (lalouxd (AT) isb (DOT) be) writes:
My knowledge about ASP is about nothing. You should try a newsgroup for ASP.

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx