Re: newlines in ADO.NET
From: headware (headware_at_aol.com)
Date: 10/08/04
- Next message: Mary Chipman: "Re: dbo. in vs generated code for stored procedures."
- Previous message: Sahil Malik: "Re: Handling column names with parenthesis..."
- In reply to: headware: "newlines in ADO.NET"
- Next in thread: chanmmn: "Re: newlines in ADO.NET"
- Messages sorted by: [ date ] [ thread ]
Date: 8 Oct 2004 11:01:43 -0700
This turned out to be a problem with the web services that we were
using to connect to the database. Apparently when the data is
serialized to XML, the \r\n turns into just a \n.
Dave
headware@aol.com (headware) wrote in message news:<e3f4b0ae.0410071508.7fa1256c@posting.google.com>...
> I'm writing an ASP.NET page containing multi-line textboxes. When I
> read them in from the HTML form the newlines are the characters "\n\r"
> which makes sense to me. However, once they have been written into
> Access, which is what my ADO.NET code is connecting to, they become
> just "\n". This is screwing up the reports that we are generating in
> Access. I've looked at the Access file through a hex editor and
> verified this. Is this a Jet Engine thing (I'm using Jet OLEDB 4.0) or
> ADO.NET thing? Is there any way to force it to write "\r\n"? I know
> there are work arounds I can do in Access or in the code to make the
> reports show up correctly, but I'd like to be able to insert "\r\n"
> into the database. That would really work out best for us.
>
> Thanks,
> Dave
- Next message: Mary Chipman: "Re: dbo. in vs generated code for stored procedures."
- Previous message: Sahil Malik: "Re: Handling column names with parenthesis..."
- In reply to: headware: "newlines in ADO.NET"
- Next in thread: chanmmn: "Re: newlines in ADO.NET"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|