RE: running out of memory
- From: "VN" <VN@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 6 Apr 2005 16:17:03 -0700
Can you post a bigger snapshot of your code? It's not clear what you do in
your loop. At what point is the memory exhausted?
"Supertree" wrote:
>
> Hi;
>
> I have to write custom data integrity utilities comparing files with table
> data.
> I've found that looping through an ado recordset will cause memory problems
> if it's a large recordset.
>
> I'm using this sort of syntax:
>
> adoRSdir = adocn.Execute(sSQL, lrecs)
>
> Do Until adoRSdir.EOF = True
> 'this loop is running out of memory
> Loop
>
> How can you monitor if you're going to run out of memory?
> What technique would be better other than narrowing the sql
> querystring result set?
>
> Thanks for your knowledge.
>
> Best Regards;
>
> Todd
>
.
- Follow-Ups:
- RE: running out of memory
- From: Supertree
- RE: running out of memory
- References:
- running out of memory
- From: Supertree
- running out of memory
- Prev by Date: RE: contents of field truncated to 255
- Next by Date: Data Link dialog always returns Connect Time value of 15
- Previous by thread: running out of memory
- Next by thread: RE: running out of memory
- Index(es):
Relevant Pages
|
|