F
Frank M.
When loading many data into a table (from many
textfiles). I start to get the error "Not enough
diskspace. You will not be able to undo this operation.
Continue (Yes/No)" or something similar (translated).
Now, my data is in text files with 200.000 - 700.000
records. I use the standard import and the records go
into a table with 5 fields, LongInts, Strings (length8) -
nothing large.
I am using Access 2002 on Windows XP with 512 Mb RAM.
The database is about 250 Mb in size. There is plenty of
free diskspace.
The strange thing is that I can load the first 3-4 files.
Then the message starts to come for every individual load
afterwards. If I reply "yes", the load completes without
incident, but sure thing next load it is there again.
It is like some kind of threshold has been reached, and
this state persists beyond the transaction of the load. I
even tried to close down Access all together, and start
again - same message comes somewhat into the load.
How can that possibly be? I can't have reached any 2 Gb
limit on the database. Could it be some kind of undo file
which Access keeps piling transactions onto, and not
reset after transaction completion?
I am wondering that perhaps repair and compression of the
database would help. Haven't tried that yet.
Well, if anyone knows of a setting that can be changed or
some other way to avoid the problem, let me know.
Regards,
Frank M.
textfiles). I start to get the error "Not enough
diskspace. You will not be able to undo this operation.
Continue (Yes/No)" or something similar (translated).
Now, my data is in text files with 200.000 - 700.000
records. I use the standard import and the records go
into a table with 5 fields, LongInts, Strings (length8) -
nothing large.
I am using Access 2002 on Windows XP with 512 Mb RAM.
The database is about 250 Mb in size. There is plenty of
free diskspace.
The strange thing is that I can load the first 3-4 files.
Then the message starts to come for every individual load
afterwards. If I reply "yes", the load completes without
incident, but sure thing next load it is there again.
It is like some kind of threshold has been reached, and
this state persists beyond the transaction of the load. I
even tried to close down Access all together, and start
again - same message comes somewhat into the load.
How can that possibly be? I can't have reached any 2 Gb
limit on the database. Could it be some kind of undo file
which Access keeps piling transactions onto, and not
reset after transaction completion?
I am wondering that perhaps repair and compression of the
database would help. Haven't tried that yet.
Well, if anyone knows of a setting that can be changed or
some other way to avoid the problem, let me know.
Regards,
Frank M.