New lines

are you letting people do <p></p> and <br> and <br /> (and also <br/>), or are you just trying to catch when they hit "enter" (creating a vbCrlf in the data), or both?

then there's two avenues you can take, with difference in the front end processing and resultant storage, but the same on display

1)
- Server.HTMLEncode the textarea's contents on the way in, all "returns" entered in the textarea are "vbCrlf"'s not <br> tags, so the encoding will leave the line breaks alone
- On the way to display, Replace(string,vbCrlf,"<br>") and line breaks work, but enterted HTML doesn't

2) (and the way i do/recommend it)
- Simply save the contents of the entered text (of course escaping the signle tics if needed)
- On the way out, do the Server.HTMLEncode on the field, then afterwards do a Replace(string,vbCrlf,"<br>")
- Since the replace of the line breaks happens after the encoding, the <br> tag will properly evaluate, while all user types HTML tags get "escaped" and show <tag>