Re: Recordset Persistence Doesn't Preserve Carriage Returns?
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Mon, 7 Aug 2006 17:38:09 -0400
Joseph Geretz wrote:
Actually, this seems to be more of an XML issue, than an ADO issue.
From the documentation I've seen, the *committee* has decided to
normalize all types of CR/LF to #xA. The commitee's decision is
final! ;-)
Perhaps I'll try to persist using ADTG format. However, the neat
thing about using XML is that this save and open can be done
completely in memory, with no need for an intermediate disk file. The
Recordset is simply saved to an in-memory DOM and then opened from
that same in-memory DOM. Can ADTG be used to perform an in-memory
clone of a recordset?
Why bother? Just disconnect the recordset and use the Clone method
whenever you need a clone.
Or are you creating a dll to be used by a server application?
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
.
- Follow-Ups:
- Re: Recordset Persistence Doesn't Preserve Carriage Returns?
- From: Joseph Geretz
- Re: Recordset Persistence Doesn't Preserve Carriage Returns?
- References:
- Recordset Persistence Doesn't Preserve Carriage Returns?
- From: Joseph Geretz
- Re: Recordset Persistence Doesn't Preserve Carriage Returns?
- From: Joseph Geretz
- Recordset Persistence Doesn't Preserve Carriage Returns?
- Prev by Date: Re: Recordset Persistence Doesn't Preserve Carriage Returns?
- Next by Date: Re: Closed Recordset from SQL Server 2000 when calling a SQL stored procedure from an ASP page
- Previous by thread: Re: Recordset Persistence Doesn't Preserve Carriage Returns?
- Next by thread: Re: Recordset Persistence Doesn't Preserve Carriage Returns?
- Index(es):
Relevant Pages
|
|