loop and update failing after 400k records

[netbumbler]

I've got a process that I'm trying to run that is a very basic loop til eof. I'm trying to build a new unique index (after adding a field to the data structure) that I'm building on the fly and then updating. Once the update is complete I simply movenext. The problem is it fails after about 400k records and sometimes it gives me an error and sometimes it runs all the way through to the eof - but doesn't update the new index field properly. (btw - the new index field is not indexed - its just for internal reference). There'a approx. 1.07M recs.
Running Access 2003 on Server 2003(on a 2000 format MDB).
Thanks for any help!
Chris

 

[Blorf]

Is there a chance that your using a variable with a max value? I can't think of one that hits at 400K, but an int for example maxes at 32K + or -.

ChaZ

There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.

 

[netbumbler]

I had that problem initially, but I long integered it and it fixed that problem. I've looked at everything I know to look at. I've compacted/repaired - no luck. I've finally settled on using a temporary data-set to do an ADD into the new dataset. This seems to work much better. I'm wondering if there's just a problem with Access2003/Windows2003 and 2gig ram and large tables/queries/updates? Are there some performance hooks for table sizes in the registry somewhere I wonder? Or something simple in Access 2003 setup? This is really pretty frustrating - it's a SIMPLE loop to EOF with a record update at each row.
Thanks,
Chris

 

[PHV]

sometimes it gives me an error
Any chance you could post the error message(s) and the highlighted line when in debug mode ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[netbumbler]

Well, this is a really strange problem that I honestly haven't seen recently. I really wonder if it could be related to Windows 2003 for sure. Here's the error:
Invalid argument runtime error -2147217887

Memory leak? Overflow of something? It's running find up until ~400k'th record.

 

[TheAceMan1]

How are ya netbumbler . . . . .

Post the code . . .

See Ya! . . . . . .

 

[netbumbler]

Ok, I've got to eat the old crow on this one. I was reviewing my code and discovered I had two strings I was referencing and I had failed to DIM one of them. Ok, give me the old water-baloon torture now... thanks.
Chris