Re: Timing Rescordset
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Fri, 1 Sep 2006 15:21:30 -0400
hgeron wrote:
Bob,
continued
The procedure was so time consuming, I decided to catch the data to an
array, and then record back to the table every 1000 lines of XML.
Since it was an array
I could deincrement the counter, and save the node.txt in the array.
This worked out to be much faster, and avoided the cancel update, and
the move last. But this still bothers me...
(1) Why does it think that node_text is a new node?
Because it is. That's more af an XML question rather than an ADO question
....
You would be better off testing the node type BEFORE adding data to the
recordset, wouldn't you?
(2) Why does the cancel update, then move last, seem to not give me
the
last record immediately, but if I put a wait, or several move last
commands, then I can be sure (usually) of getting the actual last
record.
No clue, beyond the possibility that you are running into the Jet
delayed-write behavior.
I wouldn't be using a recordset for this: I would be passing parameters to a
saved parameter query. Reply if you wish to consider that approach and I'll
give you some details.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
.
- Follow-Ups:
- Re: Timing Rescordset
- From: hgeron
- Re: Timing Rescordset
- Prev by Date: Re: Timing Rescordset
- Next by Date: Re: Timing Rescordset
- Previous by thread: Re: Timing Rescordset
- Next by thread: Re: Timing Rescordset
- Index(es):
Relevant Pages
|
Loading