Hi Jonathan,
No one quite seems to know what this means. Possibilities seem to
include:
1) An irregularity in the structure of the text file.
2) Corruption in the database you're importing into.
3) The amount of data to be imported takes the .mdb file over the 2GB
limit (even if the initial size of the .mdb file plus text file is
less than 2GB, space is needed for indexes and maybe temporary
structures).
(1) seems to be behind a lot of problems importing big text files. One
approach is to split the file in two and try importing the halves
separately. The half that won't import contains the problem record, so
split that in two and try again. Eventually this binary approach gets
everything imported except the problem record which can be
reconstructed manually.
For (3), it helps to compact the .mdb before importing. If necessary,
delete as many as possible of the indexes on the table in question,
import the data, then re-index.