H
headware
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
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