Euro ( ? ) turns up "?"

[Kim]

Inserting a record through sql (asp, msaccess textfield), inserting the euro
sign "?" shows up like a questionmark "?" in the output.

I have <%@ LANGUAGE="VBSCRIPT" CodePage=28591 LCID=2077 %> at the top of the
page where the insert statement is but still the euro sign is inserted like
something else (by looking at the data in the access database the euro sign
looks like a little square "€")

Whats wrong? Kim

 

[Dave Anderson]

Inserting a record through sql (asp, msaccess textfield), inserting
the euro sign "?" shows up like a questionmark "?" in the output.

I have <%@ LANGUAGE="VBSCRIPT" CodePage=28591 LCID=2077 %> at the top
of the page where the insert statement is but still the euro sign is
inserted like something else (by looking at the data in the access
database the euro sign looks like a little square "€")

Do you mean it is not getting into MS Access as a €, or when it is rendered
by the browser?

If the latter, you should use Server.HTMLEncode():

Response.Write(Server.HTMLEncode("€")) --> €

The browser correctly renders it and submits it as € in form elements.

 

[Anthony Jones]

Inserting a record through sql (asp, msaccess textfield), inserting the euro
sign "?" shows up like a questionmark "?" in the output.

I have <%@ LANGUAGE="VBSCRIPT" CodePage=28591 LCID=2077 %> at the top of the
page where the insert statement is but still the euro sign is inserted like
something else (by looking at the data in the access database the euro sign
looks like a little square "€")

Whats wrong? Kim

Strictly speaking the Euro symbol is not in the ISO-8859-1 codepage. (Which
is why in Dave's example Server.HTMLEncode uses a unicode entity to
represent it).

Use CodePage=1252 and ensure that the source page (where the form is
rendered) includes the code:-

Response.Codepage = "Windows-1252"

 

[Kim]

Changing the codepage seems to work. Thanks a million times for your
answers. Kim.

 

[Anthony Jones]

Strictly speaking the Euro symbol is not in the ISO-8859-1 codepage. (Which
is why in Dave's example Server.HTMLEncode uses a unicode entity to
represent it).

Use CodePage=1252 and ensure that the source page (where the form is
rendered) includes the code:-

Response.Codepage = "Windows-1252"

Oops that should be Response.CharSet