G
Guest
Hi there,
I have a large table, up to 1 million records. I run a series of queries on
this table to create what is essentially a pivot table in Access 2000. When
I do this, the process often crashes. What I want to do is process 250,000
records at a time and so build my final data table. I'm thinking of
something like using the RecordCount property for this, as in:
set rst = db.OpenRecordset("DataDump", dbOpenSnapshot)
rst.Move Last
if rst.RecordCount > 250,000 then
rst.RecordCount 1 to 250,000 ..... run my queries
if not rst.EOF
then rst 250,000 to 500,000 .... run my queries etc.
I have also thought of inserting an auto number field, in code, into my
DataDump table and using these numbers, ie:
With rst.lngRecordID (my autonumber field) 1 to 250,000 ... run my queries etc
Which of these would be best or can anyone think of a better idea.
Thanks,
All help greatly appreciated.
JR
I have a large table, up to 1 million records. I run a series of queries on
this table to create what is essentially a pivot table in Access 2000. When
I do this, the process often crashes. What I want to do is process 250,000
records at a time and so build my final data table. I'm thinking of
something like using the RecordCount property for this, as in:
set rst = db.OpenRecordset("DataDump", dbOpenSnapshot)
rst.Move Last
if rst.RecordCount > 250,000 then
rst.RecordCount 1 to 250,000 ..... run my queries
if not rst.EOF
then rst 250,000 to 500,000 .... run my queries etc.
I have also thought of inserting an auto number field, in code, into my
DataDump table and using these numbers, ie:
With rst.lngRecordID (my autonumber field) 1 to 250,000 ... run my queries etc
Which of these would be best or can anyone think of a better idea.
Thanks,
All help greatly appreciated.
JR