Sanford, Thanks so much for the reply! I think I would have torn my hair out for days trying to figure this out.
The funny part is I've been doing AJAX posts for ages, and I thought I'd done plenty of them with textareas, but maybe not. Either that, or maybe the old environment I worked in didn't use 13-10 as a line break, but rather just chr10. I'm not sure anything gets irreparably broken, but to this point, I've always treated 13/10 as a line break, and there's lots of old data in the system I've inherited that has 13/10 as line breaks, so I'll have to test to see if just treating chr(10) and ignoring chr(13) altogether gets the job done. I love ColdFusion...and I received quite the shock when that rumor floated this week that MS might buy Adobe. Not that I actually think MS will buy Adobe, but if they were to, I couldn't really imagine them supporting CF, what with .NET and all that. (Sorry to go off-topic) Ben On Oct 8, 4:08 pm, Sanford Whiteman <[email protected]> wrote: > > I've never seen this before, and I've certainly used Form.Request in > > the past, so I'm sort of beating my head against a wall. I've tested > > this both on my laptop (Windows 7, IIS 7, ColdFusion 9), and our > > production box (Windows Server 2003, IIS6, ColdFusion 8), and get the > > same results. > > Great to see CF in use, BTW. My one CF client had to phase out when > they put in a new CMS -- boo! > > As in that guy's ASP.NET example, you should be able to deal with this > server-side by just replacing in a CRLF before storing the data, no? > What's the case in which this irreparably breaks something? > > -- S.
