Carriage Return and Response.Write Output Issue

>I have a field in a SQL Server table named DetailedDescription that is
a varchar. If the user adds/edits a detailed description, they do so
in a MulltiLine TextBox control. Therefore, they are able to click
enter on their keyboard and have multiple carriage returns inside the
DetaildDescription.
>
My problem is that I have another webpage in my project that has the
following statement in it:
Response.Write(drSQL.Item("DetailDescription")).
>
If the user created a record in the following format:
HELLO
WORLD
>
It is now displayed as:
HELLO WORLD
>
Is there something I can add to my Response.Write statement so that the
carriage returns are "written" so that the output is in the following
format:
HELLO
WORLD
>
I hope this makes sense.
>
>
Thanks,
CR Junk
>

I have a field in a SQL Server table named DetailedDescription that is
a varchar. If the user adds/edits a detailed description, they do
so in a MulltiLine TextBox control. Therefore, they are able to
click enter on their keyboard and have multiple carriage returns
inside the DetaildDescription.
>
My problem is that I have another webpage in my project that has the
following statement in it:
Response.Write(drSQL.Item("DetailDescription")).
>
If the user created a record in the following format:
HELLO
WORLD
>
It is now displayed as:
HELLO WORLD
>
Is there something I can add to my Response.Write statement so that
the carriage returns are "written" so that the output is in the
following format:
HELLO
WORLD
>

Thanks for the responses. I ended up using Gomer's suggeetion.
>
CR Junk

Hi, if i were you, i would use the same as Gomer's but with little
modification
Response.Write(replace(drSQL.Item("DetailDescripti on"),chr(13),"<BR>")
>
what i did is that i replaced the vbCrLf to chr(13), because the vbCrLf
is combination of chr(13) and chr(10), so what if the user had used a
format that he only included the chr(13), then if you use the vbCrLf it
will not work, because using the vbCrlf will look for the two at once
which only one is available. And by the way, according to me testings,
chr(13) is required for the enter more than the chr(10) which means
chr(10) is always to occure.
And if you still want to use his advice, then use it this way: use vbCr
instead of chr(13)
>

>
Best Regards
Firas S Assaad
crjunk wrote:>

>
"Firas" <firas489@gmail.comwrote in message
news:1161052940.189145.108950@m7g2000cwm.googlegro ups.com...>
There are two end-of-line markers in common use. CRLF or just plain LF.
I've not come across many (in fact never have) systems that only use CR.
What tests did you use to discover that CR on it's own is more common or
indeed ever happens at all?
>
My solution BTW is :-
>
Replace(Replace(Server.HTMLEncode(s), vbCR, ""), vbLF, "<br />")
>
>
>
>>
>

we're talking about someone hitting the enter key in text area on a
web page...
how would this ever be translated into anything other than crlf??
>
>
"Anthony Jones" <Ant@yadayadayada.comwrote in message
news:eN9yaOe8GHA.4476@TK2MSFTNGP04.phx.gbl...

we're talking about someone hitting the enter key in text area on a web
page...
how would this ever be translated into anything other than crlf??
>

>
"Anthony Jones" <Ant@yadayadayada.comwrote in message
news:eN9yaOe8GHA.4476@TK2MSFTNGP04.phx.gbl...>
>