>Why not change the chr(13)? The issue is that SQL eats the chr(13) and I need the line breaks to be as entered, so I change it 1) to something that I wouldn't use usually, and 2) something that HTML would understand, since certain records get exported for HTML display.
They are entered just you didn't see them with SSMS. hides these chars.
I don't know why, maybe the grid control used to show data has this behavior, but the line break is there.
>As far as the 'True' vs .t., SQL, at least our set up, doesn't like/understand .t. being passed in.
Then maybe you use Char fields not BIT one?
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.