>>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.

Not so far as I've noticed, when I bring it back and do AT(chr(13), script) it returns 0 and display (editbox) shows no line breaks
>
>>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?

Nope, defined as BIT - but none of this explains the error. All of this was in place before I started getting this S1007 error